[ci] Better reporting on invalid JUnits #12222
Closed
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
This makes it so parsing JUnits is not an all-or-nothing proposition. Now failures are put into a side channel and reported but they do not affect other JUnits. This also improves reporting a bit so we can see if the `pytest_wrapper.py` script has failed or not.
|
we just need to update the junitparser in the qemu image to 2.4.2 |
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 it so parsing JUnits is not an all-or-nothing proposition. Now failures are put into a side channel and reported but they do not affect other JUnits. This also improves reporting a bit so we can see if the
pytest_wrapper.pyscript has failed or not.Fixes #11749
cc @Mousius @areusch