CI: CircleCI seems to occasionally time out, increase the limit#18353
Merged
charris merged 1 commit intonumpy:maintenance/1.20.xfrom Feb 7, 2021
Merged
CI: CircleCI seems to occasionally time out, increase the limit#18353charris merged 1 commit intonumpy:maintenance/1.20.xfrom
charris merged 1 commit intonumpy:maintenance/1.20.xfrom
Conversation
CircleCI seems to default to a 10 minute timeout on no output, simply increase it to 30 minutes to ensure the build should succeed. It seems the build does take 25+ minutes (maybe depending on the machine it runs on). Technically, 30 minutes is probably more than necessary, since there is a print in the middle, but that is just a warning that could go away at some point.
This was referenced Mar 8, 2021
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
2 participants
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.
Backport of #18349.
CircleCI seems to default to a 10 minute timeout on no output,
simply increase it to 30 minutes to ensure the build should
succeed.
It seems the build does take 25+ minutes (maybe depending on the
machine it runs on). Technically, 30 minutes is probably more than
necessary, since there is a print in the middle, but that is
just a warning that could go away at some point.