-
-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Treat empty input strings as None #198
Merged
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
This comment has been minimized.
This comment has been minimized.
Unit Test Results (Test Files) 24 files ±0 4 errors 21 suites ±0 39m 12s ⏱️ ±0s For more details on these parsing errors, failures and errors, see this check. Results for commit 3949fda. ± Comparison against base commit fbe06cd. ♻️ This comment has been updated with latest results. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
EnricoMi
force-pushed
the
branch-treat-empty-input-strings-as-none
branch
from
November 30, 2021 22:56
f9c9087
to
99b0351
Compare
EnricoMi
force-pushed
the
branch-treat-empty-input-strings-as-none
branch
from
November 30, 2021 22:58
db33737
to
3949fda
Compare
ilent2
pushed a commit
to ilent2/publish-unit-test-result-action
that referenced
this pull request
Dec 13, 2021
ilent2
added a commit
to ilent2/publish-unit-test-result-action
that referenced
this pull request
Dec 13, 2021
This reverts commit 1976f65.
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.
Composite action calls into the Docker image and sets all supported inputs. Here, originally unset inputs are set as empty strings:
publish-unit-test-result-action/composite/action.yml
Lines 115 to 138 in fbe06cd
The
event_file
arguments turns out to be the only effected by this, all other have defaults forNone
and empty strings. This PR turns empty input strings into properNone
s. This makes the "running-on-a-fork-PR" check inmain
work for the composite action (wheresettings.event_file
is notNone
but an empty string):publish-unit-test-result-action/python/publish_unit_test_results.py
Lines 63 to 71 in fbe06cd
As @BlasiusSecundus showed in #188 (comment), the composite action fails on a fork PR because it tries to write-access the API, which fails with 403, which is retried. We have to retry all 403 because we cannot distinguish between 403 responses that are retry-able due to rate-limit (#150, #170) and those that are not retry-able because we are running in a fork repository context (#167). The "running-on-a-fork-PR" check is supposed to avoid the latter case.