Add more data artifacts when CI fails#1176
Merged
Conversation
jeffreyt
force-pushed
the
more-data-on-ci-fail
branch
from
c2d8269 to
77f2e2c
Compare
Collaborator
Author
|
rebased with develop |
pagrubel
approved these changes
Mar 31, 2026
Collaborator
pagrubel
left a comment
pagrubel
left a comment
There was a problem hiding this comment.
Thanks, I was able to test this with failing tests of another PR.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ci/env.sh sets a bunch of useful variables, after the first time it runs, capture them in $GITHUB_ENV which makes them accessible downstream
downstream add a new step in case of failure to dump them in a single directory, modify following step to save the single directory as an artifact
So far I added:
We can also add anything else we may need to examine here.