buildsys: retry builds on "unexpected EOF" error #1557
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 is a rare failure that we see in CI. Retry it so the entire run is not marked as failing. Co-authored-by: Ben Cressey <[email protected]> Co-authored-by: Tom Kirchner <[email protected]>
bcressey
approved these changes
May 4, 2021
webern
approved these changes
May 4, 2021
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.
Issue number:
#1095
Description of changes:
This is an alternate approach to #1545 that uses regexes to give us a little more control over how we match messages. In particular, it at least lets us make sure that "unexpected EOF" is on a line of its own, and not embedded in any other build message.
Testing done:
stdoutto test this, because RPM prefixes every line of output and it wouldn't match as a full line otherwise.Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.