Align dependency library versions in building and running stage #23
Conversation
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
Jonathanlyj
changed the title
|
Please also apply the same changes to those GitHub workflow yaml files. |
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.
There was a problem with "pip install ." caused by mismatched mpi4py versions in build stage and run stage. Building stage used mpi4py 4.0.0 and generated "mpi4py.MPI.Session" codes which causes an incompatibility error when running the project with mpi4py 3.1.x.
Forcing building and running stage to use a specific version number (by specifying mpi4py<4.0.0 ) works but is not ideal because it limits user's options (either mpi4py 3.x.x or mpi4py 4.0.0). Instead, we can add -no-build-isolation to pip install to force building stage to use whatever already installed if satisfies the version requirements. Build dependencies must be already installed if this option is used. In this case, "wheel" and "packaging" need to be manually installed by user.