Release 0.10.4#1481
Merged
Merged
Conversation
With the bug fix PRs all backported this commit bumps the version string to indicate this is the next bugfix release.
This flag enables several unsafe floating-point transformations that are not generally appropriate for a distributed mathematical library. Most importantly, however, `-ffast-math` on `gcc` also forcibly enables the floating-point "flush to zero" mode for subnormal numbers when the dynamic library is loaded, which affects not just Qiskit Aer, but every other floating-point operation in the running process. This is not our decision to make for users, and it shouldn't be distributed.
The aer gpu package wheel job for python 3.10 builds in the manylinux2014 container image, while for the older Python versions it uses the manylinux2010 image. The manylinux2014 image is based on Centos 7 while the manylinux2010 image is based on Centos 6. During the qiskit-aer 0.10.3 release the gpu wheel job failed because when running the py3.10 build we installed the cuda package for centos 6 in the manylinux2014 centos 7 based image. This caused the job to fail when nvcc was called because it was not installed properly. To fix this issue the Python 3.10 build is split out into a separate job. This separate job will install the same cuda version but for centos 7 which is appropriate for the manylinux2014 image.
…#1467) * Change not to fail to run noisy simulation with T2 > 2 * T1 Previously NoiseModel.from_backend failed when T2 value is greater than 2 * T1, however, sometimes backend returns such T2 value. This change truncates T2 value up to 2 * T1 with issuing a user warning. Co-authored-by: Hiroshi Horii <horii@jp.ibm.com>
Member
|
Just marking as on hold until all the required PRs to main are merged and then backported as part of this PR |
…#1480) * Enable cacheblocking of superop operations and fix a bug in measurement with multi-chunks Previously, superop was not recognized in transplation of cacheblocking and then it was not correctly handled in multi-gpu environment and hybrid environment with gpu and cpu. This change enhance cacheblocking for superop and then make density matrix simulation with GPU(s) correctly. In addition, a measurement issue with cacheblocking was also fixed.
The 3.1 release of Jinja breaks some part of the Sphinx/nbsphinx pipeline, causing tutorial jobs to fail. The jinja2 developers consider this a Sphinx bug, so we need to pin Jinja until a new version of Sphinx or the nbsphinx extension is released to fix the issue.
* Add a size of required memory in an error message Previously there is no way to know required memory to simulate a circuit when simulation fails due to shortage of memory. This change adds required memory and available max memory in a message of error state.
The to_json() method is called for each circuit header. A header may include metadata and metadata can be a python object. This PR changes serialization of circuit headers to use py::handle without serializing to a json. Fixes Qiskit#1435 * use python parser for circuit.header * support metadata copy with parameterization * avoid serialization of circuit metadata * use circuit_index to specify metadata * remove metadata from qobj for Aer to simulate circuits * add release note * clear circuite metadata correctly. * take unnecessary tests for circuit metadata backup/recovery * work around metadata serialization issue within _run method * Update releasenotes/notes/remove_circuit_metadata_from_qobj-324e7ea9b369ee67.yaml
Collaborator
Author
Member
|
It looks like the test failures are real I expect that #1496 is causing a segfault or similar error causing linux and macos to fail on: |
Collaborator
Author
Another possibility is that thrust performance issue resolved in #1497 (via #1498) produces timeout. But, yes, #1496 is necessary for this release, I think. |
Member
Collaborator
Author
Member
|
Thanks, this LGTM. I think we just need to backport #1501 now and then I think we are ready to release |
The BaseBackend class in qiskit-terra (along with the rest of the legacy provider interface) is deprecated and being removed soon in Qiskit/qiskit#7886. To avoid potential compatibility issues or deprecation warnings we shouldn't be using this class anymore. This commit removes the last 2 uses of these legacy classes to avoid issues moving forward. Co-authored-by: Hiroshi Horii <hhorii@users.noreply.github.com> (cherry picked from commit 07a8532)
mtreinish
approved these changes
Apr 6, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Summary
Release 0.10.4 to fix bugs.
Details and comments