Add CI job to run unittests under MPI #1244
Open
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
In Qiskit#1242 we added a basic smoke test job for MPI builds using standalone mode. That job builds aer in standalone mode with MPI and then runs a qobj of a grovers circuit with mpi enabled and validate it works (and the result metadata has the mpi fields set). That was useful to provide a quick smoke test to verify that a proposed change doesn't completely break MPI builds. However, it doesn't fully validate aer's usage with MPI enabled. This commit adds a new CI job that runs the full python unittest suite under mpi run using a aer binary built with mpi support. The tradeoff there though is we have to run the tests serially using the stdlib python unittest runner (since stestr runs tests in parallel processes) the process is running under mpirun. Additionally, this commit bumps the timeout for the unit test jobs to 1 hour as we've been regularly hitting the timeout on the CI test jobs. The timeout for the new mpi job is double that (120 min) since it is running tests serially instead of in 2 or 4 processes.
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.
Summary
In #1242 we added a basic smoke test job for MPI builds using standalone
mode. That job builds aer in standalone mode with MPI and then runs a
qobj of a grovers circuit with mpi enabled and validate it works (and
the result metadata has the mpi fields set). That was useful to provide
a quick smoke test to verify that a proposed change doesn't completely
break MPI builds. However, it doesn't fully validate aer's usage with MPI
enabled. This commit adds a new CI job that runs the full python unittest
suite under mpi run using a aer binary built with mpi support. The
tradeoff there though is we have to run the tests serially using the
stdlib python unittest runner (since stestr runs tests in parallel
processes) the process is running under mpirun.
Additionally, this commit bumps the timeout for the unit test jobs to 1
hour as we've been regularly hitting the timeout on the CI test jobs.
The timeout for the new mpi job is double that (120 min) since it is
running tests serially instead of in 2 or 4 processes.
Details and comments