Ignore specific deprecation warnings in stable-latest tests #90
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
|
All of the |
lillian542
approved these changes
Oct 1, 2024
Good idea, I'll add one. |
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.
As name says. The latest version of the failing plugins have already been updated to no longer use the deprecated code, so we're left with false positives in the stable-latest tests. This PR suppresses the
QubitDeviceandQubitStateVectordeprecation warnings for the stable-latest tests.Note that the latest-latest test workflows have also been updated because I made some formatting changes to the template file. These changes are superficial and don't change the latest-latest tests in any way.