Delete ibmq tests #579
Merged
Delete ibmq tests #579
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
[sc-69774] |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #579 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 9 9
Lines 867 867
=========================================
Hits 867 867 ☔ View full report in Codecov by Sentry. |
soranjh
approved these changes
Jul 29, 2024
obliviateandsurrender
approved these changes
Jul 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
ibmq_tests.ymlfile tests two files, namelytest_ibmq.pytest_runtime.py, that have been deleted with the merging of the new Qiskit Device. This PR removed theibmq_tests.ymlfile.We no longer have these ibmq tests because there is no cloud simulator for us to run the tests on anymore. We don't have any tests that require an IBM Quantum account token at the moment (we use local simulators for everything). There is the option to replace these tests with tests that use a real IBM device, but that would potentially require a paid plan depending on the number of calls to the backend.