Skip to content
This repository was archived by the owner on Aug 19, 2023. It is now read-only.

Avoid using FakeMelbourne from qiskit/test#301

Merged
mtreinish merged 4 commits intoQiskit:masterfrom
mtreinish:no-vcr-benchmarks
May 24, 2019
Merged

Avoid using FakeMelbourne from qiskit/test#301
mtreinish merged 4 commits intoQiskit:masterfrom
mtreinish:no-vcr-benchmarks

Conversation

@mtreinish
Copy link
Copy Markdown
Member

Summary

In the previous update to the the quantum volume benchmarks the fake
melbourne class from the terra tests was used instead of hardcoding the
coupling map directly in the benchmark. However because this lives in
the terra tests python namespace it has a depedency on a bunch of test
requirements at import time (even though they're not used). This causes
the benchmarks to fail in a production environment because they do not
install the terra development/testing requirements in the venv used for
testing. To avoid this failure, this commit removes the fake backend
usage and switches to a hard coded coupling map which was just copied
from the backend code. [1]

Details and comments

[1] https://github.com/Qiskit/qiskit-terra/blob/master/qiskit/test/mock.py#L258-L260

mtreinish added 4 commits May 24, 2019 10:45
In the previous update to the the quantum volume benchmarks the fake
melbourne class from the terra tests was used instead of hardcoding the
coupling map directly in the benchmark. However because this lives in
the terra tests python namespace it has a depedency on a bunch of test
requirements at import time (even though they're not used). This causes
the benchmarks to fail in a production environment because they do not
install the terra development/testing requirements in the venv used for
testing. To avoid this failure, this commit removes the fake backend
usage and switches to a hard coded coupling map which was just copied
from the backend code. [1]

[1] https://github.com/Qiskit/qiskit-terra/blob/master/qiskit/test/mock.py#L258-L260
@mtreinish mtreinish merged commit 7e24acc into Qiskit:master May 24, 2019
@mtreinish mtreinish deleted the no-vcr-benchmarks branch May 24, 2019 15:59
jakelishman pushed a commit to jakelishman/qiskit-terra that referenced this pull request Aug 1, 2023
…#301)

In the previous update to the the quantum volume benchmarks the fake
melbourne class from the terra tests was used instead of hardcoding the
coupling map directly in the benchmark. However because this lives in
the terra tests python namespace it has a depedency on a bunch of test
requirements at import time (even though they're not used). This causes
the benchmarks to fail in a production environment because they do not
install the terra development/testing requirements in the venv used for
testing. To avoid this failure, this commit removes the fake backend
usage and switches to a hard coded coupling map which was just copied
from the backend code. [1]

[1] https://github.com/Qiskit/qiskit-terra/blob/master/qiskit/test/mock.py#L258-L260
jakelishman pushed a commit to jakelishman/qiskit-terra that referenced this pull request Aug 11, 2023
…#301)

In the previous update to the the quantum volume benchmarks the fake
melbourne class from the terra tests was used instead of hardcoding the
coupling map directly in the benchmark. However because this lives in
the terra tests python namespace it has a depedency on a bunch of test
requirements at import time (even though they're not used). This causes
the benchmarks to fail in a production environment because they do not
install the terra development/testing requirements in the venv used for
testing. To avoid this failure, this commit removes the fake backend
usage and switches to a hard coded coupling map which was just copied
from the backend code. [1]

[1] https://github.com/Qiskit/qiskit-terra/blob/master/qiskit/test/mock.py#L258-L260
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants