fix(ci): stop reporting healthy dump runs as failed - #62
Merged
Merged
Conversation
refresh-data: upload-artifact crashed with "Maximum call stack size exceeded" on the ~1M-file dump; it now uploads one tar.gz. dump-refresh: create-pull-request could fail with GitHub's "diff is taking too long to generate" after the PR already existed (TechAPI #180). That step now continues, and a follow-up fails the job only when no open PR exists for the branch. Refs #1
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
1 participant
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.
tar.gzbeforeupload-artifact(crashed with Maximum call stack size exceeded on ~1M files, run 34923333120).create-pull-requestgetscontinue-on-error; a new step fails the job only if no open PR exists for the branch. Run 34923332763 failed with diff is taking too long to generate although TechAPI #180 was created.Refs #1