Better report of failures, append stderr/out. #3450
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.
This is a follow-up to #3403 -- I've noticed that the
xmllint --xpath '//testsuite/testcase[./failure]/@name' $file | cut -f2 -d '='
only selects the 1st failed test, in case there are more failed cases in the testsuite.During last hunt for a CI-failing test (that did not fail on local at all), I've also missed stderr/out for the failed suite. And also the actual assert stacktrace, since not all asserts have String message, the stacktrace can help to identify the exact failure.
Now the output is as follows:
I broke several files so that this PR's checks output will show the effect.