Adjust env vars instead of using venv activate #16669
Merged
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.
Follow-up to PR #16644 and #16560
This PR (along with PR #16663) is intended to resolve warnings in nightly
testing like this
The venv activate script stores the absolute path but that causes
problems in case it changes (e.g. if
CHPL_HOME
is renamed or in thecase of module builds).
So, this PR changes
run-in-venv.bash
andrun-in-test-venv.bash
toadjust environment variables directly rather that using the activate
script. It also adjusts c2chapel to use
run-in-venv.bash
instead of theactivate script.
Reviewed by @lydia-duncan - thanks!