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 hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
MAX_JOBS=20environment variable is set for the standard tests but not for the multi-gpu tests (line 212). This creates an inconsistency where the two test jobs may behave differently during compilation.Consider either:
MAX_JOBS=20to the multi-gpu job as well for consistency, ordocker exec -e MAX_JOBS=20) in both jobsAdditionally, note that the multi-gpu job uses
docker exec -e MULTIGPU=TRUE(line 209) which is a more standard way to pass environment variables to docker exec, while this change usesbash -c "MAX_JOBS=20 ..."which sets it within the bash command. The-eflag approach would be clearer and more consistent.