Skip to content

v5.0.x: mpi4py: run the spawn and dynamic process tests #12450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

jsquyres
Copy link
Member

@jsquyres jsquyres commented Apr 2, 2024

Split the mpi4py Github Action into 4 parts:

  1. build: do everything to build, configure, and install Open MPI and mpi4py
  2. run: run all the mpi4py tests with its defaults. As of March 2024, this disables the spawn and dynamic tests, which means that the entire block of tests should pass.
  3. run_spawn: run all the mpi4py tests, including the spawn tests, but only if the "mpi4py" label is set on the PR. As of March 2024, we know some of these tests are failing.
  4. run_dynamic: run all the mpi4py tests, including the dynamic tests, but only if the "mpi4py" label is set on the PR. As of March 2024, we know some of these tests are failing.

The spawn and dynamic failures are different, so we split them up and run them separately.

For steps 2, 3, and 4, we utilize a reusable Github workflow so that we don't have to duplicate the code.

Signed-off-by: Jeff Squyres jeff@squyres.com
(cherry picked from commit deb4bda)

This is the v5.0.x PR corresponding to main PR #12421

Split the mpi4py Github Action into 4 parts:

1. build: do everything to build, configure, and install Open MPI and
   mpi4py
2. run: run all the mpi4py tests with its defaults.  As of March 2024,
   this disables the spawn and dynamic tests, which means that the
   entire block of tests should pass.
3. run_spawn: run all the mpi4py tests, including the spawn tests, but
   only if the "mpi4py" label is set on the PR.  As of March 2024, we
   know some of these tests are failing.
4. run_dynamic: run all the mpi4py tests, including the dynamic tests,
   but only if the "mpi4py" label is set on the PR.  As of March 2024,
   we know some of these tests are failing.

The spawn and dynamic failures are different, so we split them up and
run them separately.

For steps 2, 3, and 4, we utilize a reusable Github workflow so that
we don't have to duplicate the code.

Signed-off-by: Jeff Squyres <jeff@squyres.com>
(cherry picked from commit deb4bda)
@github-actions github-actions bot added this to the v5.0.3 milestone Apr 2, 2024
@wenduwan wenduwan merged commit c114600 into open-mpi:v5.0.x Apr 9, 2024
@jsquyres jsquyres deleted the pr/v5.0.x/mpi4run-run-the-spawn-tests branch September 2, 2024 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants