Repository navigation
Retry transient GitHub Check publication updates - #137
Merged
Merged
Conversation
This file contains hidden or 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
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.
JUnit Check publication can fail when GitHub accepts Check creation but immediately returns 404 for the completion PATCH, leaving a successful suite's report in progress.
Retry only that same PATCH twice, after 1 and 3 seconds, through a fetch preload scoped to the pinned test-reporter action. Check creation, other requests/statuses and network errors are not retried; exhausting the attempts preserves the error. The request body and test conclusion remain unchanged. Inline workflow code preserves trusted fork reporting without checking out PR code, and the Actions Summary is unchanged.
Validation:
bundle exec fastlane android python_checkswith pinned dependencies (85 tests); actual Node preload/fetch against a local HTTP fixture returning two 404s followed by 200; YAML parsing, Node syntax andgit diff --check. Confirmed that the pinned reporter's Octokit uses global fetch. Added six regression tests and synchronized EN/RU testing policy.APK artifacts
Built from commit
5bafc49cby CI run #452.Artifacts expire after 14 days. Neither APK uses the MegaProxy release key.