ci: dump failure details on test failure #270
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
liamstask
force-pushed
the
test-verbosity
branch
from
611599a to
b259de3
Compare
Codecov Report
@@ Coverage Diff @@
## master #270 +/- ##
=========================================
Coverage ? 78.97%
=========================================
Files ? 157
Lines ? 12997
Branches ? 0
=========================================
Hits ? 10265
Misses ? 2732
Partials ? 0Continue to review full report at Codecov.
|
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.
the failed ci run for #264 doesn't have many actionable details about what failed.
by setting the
CTEST_OUTPUT_ON_FAILUREenvironment variable, the ctest runner will at least dump details about which assertions failed in the event of a failure, which should help with diagnosis.