chapel-py: Add environment variables to always build chapel-py and CLS #24912
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
I envision this being helpful for eventually getting chapel-py and friends auto-tested nightly. Signed-off-by: Danila Fedorin <daniel.fedorin@hpe.com>
DanilaFe
changed the title
jabraham17
approved these changes
Apr 23, 2024
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.
Fixes #24871.
This PR adds two more environment variables,
CHPL_ALWAYS_BUILD_CHAPEL_PYandCHPL_ALWAYS_BUILD_LANGUAGE_SERVER, to buildchapel-pyandchpl-language-serveronmake -j32. This will help in situations such as setting offparatests: simply runningmake -j32will be enough to make sure that Python environment is up to date, ensuring thatchplcheck(etc.) tests run. This should help catchchplcheckbugs as they come up.Reviewed by @jabraham17 -- thanks!