Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updateing master #8

Merged
merged 35 commits into from
Nov 21, 2023
Merged

updateing master #8

merged 35 commits into from
Nov 21, 2023

Conversation

shef4
Copy link
Owner

@shef4 shef4 commented Nov 21, 2023

No description provided.

NoureldinYosri and others added 30 commits October 26, 2023 18:47
quantumlib#6328)

* Move all pytest_collection_modifyitems hooks to the top conftest.py and
  apply mark-based test-selection there
* Move custom marks definitions to pyproject.toml
  so they show in `pytest --markers`
* Add custom pytest option `--enable-slow-tests` to run slow-marked tests.
  These are otherwise skipped by default.
* Support a quick check of test selection using
  `pytest --co -m skip` and `pytest --co -m "not skip"`

Partially implements quantumlib#6211
---------

Co-authored-by: Pavol Juhas <[email protected]>
…6331)

* Add slow marks to the unit tests with over 20 second duration.
* Update the ci-daily job so it runs all slow tests.
* Add ci-daily jobs for Windows and MacOS operating systems
  so that slow tests are tested on these platforms too.

Refs: 
* quantumlib#6211 (comment)
* quantumlib#6211 (comment)

Resolves quantumlib#6211
No change in the test execution, just a bit more output for the
`Pytest Ubuntu`, `Pytest Windows`, and `Pytest MacOS` jobs.

Related to quantumlib#6211
* Fix requirements installation for Windows
* Run notebook tests only on Linux platform
* Run test_isolated_packages on POSIX platforms only

Temporary workaround for quantumlib#6336
Exercise the `open_in_browser` argument from the
test_generate_html_file_with_browser test, but do
not affect the actual browser session.
This caches various computed properties on `Circuit` so that they do not need to be recomputed when accessed if the circuit has not been mutated. Any mutations cause these properties to be invalidated so that they will be recomputed the next time they are accessed.
Increase tolerance for fidelities calculated with and without state
vector amplitudes.  Avoid flaky test failures due to round-off errors.

Example: https://github.com/quantumlib/Cirq/actions/runs/6726576064/job/18283075054#step:6:598
…uantumlib#6345)

* StreamManager: retry with get result request on already exist errors

* Fix unused import

* Clarified comment for 'program already exists' retry
* Update start.ipynb

Update the start notebook with the new start notebook that details how to run against our hardware. Notably, only people with access can run circuits against our hardware.

* Update start.ipynb

lint

* Update start.ipynb

attach --pre flag to cirq install for stable version

* Update start.ipynb

Put in default value for processor_id

* Update start.ipynb

add Black as default. This _shouldn't_ run against actual hardware since a valid project_id is never specified. A valid `processor_id` however is needed to pass the CI.

* Update start.ipynb

populate default project_id

* set virtual=True to pass CI check

* Update start.ipynb

make default processor_id an empty string now that `virtual=True` is set

* Update start.ipynb

add back processor_id so it matches current merged version

* Update start.ipynb

rm `cirq --pre` install

* Update start.ipynb

delete overriding instance of `engine`

* Update start.ipynb

fix

* Update start.ipynb

nit

* Update start.ipynb

Add back original fix to known issue nteract/papermill#519

* Update start.ipynb

resolve nit
* Update docs/tutorials/google/start.pynb

* address comments
on 3+ qubits into single qubit measurements
if -and only if- the result isn't stored (i.e. key is None)
and test for changes in RoutCQC
removed unintended change
updates from review- varible names, ciruit build
@shef4 shef4 merged commit 8b7ef8e into master Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants