use chapel-blog sources inside chapel/test #26033
Merged
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
Signed-off-by: Ahmad Rezaii <ahmad.rezaii@hpe.com>
riftEmber
reviewed
Oct 3, 2024
riftEmber
approved these changes
Oct 3, 2024
Signed-off-by: Ahmad Rezaii <ahmad.rezaii@hpe.com>
arezaii
force-pushed
the
move-chapel-blog-test-dir
branch
from
63e4f65 to
b114a03
Compare
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.
This makes a minor change to the nightly script when testing the chapel-blog. Instead of testing from a directory external to
$CHPL_HOME, now the relevant blog sub directories will be copied into$CHPL_HOME/test/copied-chapel-blog/so that reports on failures will not include the full path, which was exposing test machine directory structure.TESTING:
test-linux64-llvm16.bash[reviewed by @riftEmber - thanks!]