Avoid deprecation warnings coming from terra
See original GitHub issueWhat is the expected behavior?
The test suite currently emits several deprecation warnings, mostly due to the use of qiskit.compile()
, which is to be deprecated in 0.9. We should move the tests to use the new transpilation workflow accordingly.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Any way to disable new deprecation warnings? - Terraform
Any way to disable new deprecation warnings? ... So as of the latest Terraform binary from last week, I'm now being flooded with...
Read more >java - How to avoid deprecation warnings when ...
Recently we decide to deprecate a class. The problem is in some cases @SuppressWarnings("deprecation") will not suppress the deprecation warning ...
Read more >The Complete Guide for Deprecation Warnings in Rails
When it comes to production, the easiest way to discover deprecation warnings is by using a monitoring tool (like Honeybadger or Airbrake).
Read more >Warning: Helpful Warnings Ahead - Kubernetes
During the deprecation period, the pre-release API remains functional, allowing several releases to transition to the stable API version.
Read more >Release Notes - Qiskit
Qiskit Metapackage Version qiskit‑terra qiskit‑aer qiskit‑ibmq‑provider Release Date
0.39.4 0.22.3 0.11.2 0.19.2 2022‑12‑08
0.39.3 0.22.3 0.11.1 0.19.2 2022‑11‑25
0.39.2 0.22.2 0.11.1 0.19.2 2022‑11‑03
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You mean I’m actually going to have to think?! No fair! 😃 Thanks for the help, @diego-plan9 , I’ll continue to work on this.
Cool, thanks again! I’d suggest tackling them in separate PRs, even if both are test-related.
Usually the output of running
make test
locally would work - even if it might be a bit messy. Failing that, another way would be to look at the travis logs - for example, the latest master commit at https://travis-ci.com/Qiskit/qiskit-ibmq-provider/jobs/190031347 shows warnings such as:Those lines would hopefully point towards where the deprecated instruction is being used (
test.ibmq.test_ibmq_backends.TestIBMQBackends.test_qobj_headers_in_result_sims
), and hints on what the new behaviour is (in this case, replacing thecompile(..)
at 97).