Fix failing on no files #543
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
EnricoMi
changed the title
Test Results (Test Files) 145 files ±0 13 errors 735 suites ±0 2h 12m 37s ⏱️ ±0s For more details on these parsing errors, failures and errors, see this check. Results for commit f9d52c1. ± Comparison against base commit 3cd0197. ♻️ This comment has been updated with latest results. |
EnricoMi
force-pushed
the
fix-inconclusive-conclusion
branch
from
4e93c86
to
19421ff
Compare
kfr2
pushed a commit
to turnitin-actions/publish-unit-test-result-action
that referenced
this pull request
Feb 13, 2024
* Fix failing on no files (Inconclusive conclusion is actually called neutral) * Log inconclusive when conclusion is neutral
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.
Inconclusive conclusion is actually called "neutral" internally.