Jenkinsfile: collect junit.xml for all architectures #39719
Merged
Conversation
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
Member
Author
|
Working! This is what it looks now, with unit test results collected from x86, s390x ("z"), and PowerPC |
8 tasks
Member
Author
|
@andrewhsu @tiborvass ptal |
This will send the results directly after the tests complete, and make the stage more atomic. Signed-off-by: Sebastiaan van Stijn <[email protected]>
Jenkins groups them per stage, so collecting them for all architectures is possible (without them conflicting or becoming ambiguous) Signed-off-by: Sebastiaan van Stijn <[email protected]>
thaJeztah
force-pushed
the
junit_all_stages
branch
from
d3c2e8c to
e2f5b78
Compare
Member
Author
|
Rebased; no changes were needed during rebase |
tiborvass
approved these changes
Aug 13, 2019
This was referenced Aug 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Addresses parts of #39675
In case a job fails before even generating a report file. (cherry-picked from Reduce time of integration tests #39682)
This will send the results directly after the tests complete, and make the stage more atomic.
Jenkins groups them per stage, so collecting them for all architectures is possible (without them conflicting or becoming ambiguous)