[Build] Always collect test-results and don't fail on test-failures #3148
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
HannesWell
force-pushed
the
adjust-workflow-for-test-publication
branch
from
8807c2e to
f7d8476
Compare
Merged
The 'Publish Unit Test Results' introduced with eclipse-xtext#3144 will fail if test-failures are found.
HannesWell
force-pushed
the
adjust-workflow-for-test-publication
branch
from
f7d8476 to
a0c94e4
Compare
Test Results 3 240 files + 3 240 3 240 suites +3 240 1h 41m 22s ⏱️ + 1h 41m 22s For more details on these failures, see this check. Results for commit a0c94e4. ± Comparison against base commit 7a17f87. |
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 'Publish Unit Test Results' introduced with #3144 will fail if test-failures are found.
The test-result should always be collected, otherwise the test result publication cannot show the number of passed tests.