Tighten CI job timeout down to 15min #937
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
|
The first test failure appears completely unrelated, rather just a ##[debug]/usr/bin/bash -e /home/runner/work/_temp/29af068a-7dc7-405e-bd92-171e9757ad02.sh Volta error: Could not download [email protected] from https://registry.npmjs.org/yarn/-/yarn-1.22.5.tgz |
|
It looks like some of the windows tests exceed the 15 minute window. So we will likely need to split them, or reduce their times. cc @thoov |
Speaking with the team, we would love to reach a 10 minute Commit -> CI feedback loop goal. (Assuming the GH Actions queue depth isn't too deep) We have spoken with GH to increase our concurrency, but in-order to reach our goal each of our jobs cannot exceed 5->8minutes. This is a first step in locking that in.
stefanpenner
force-pushed
the
tighten-timeouts
branch
from
87b9552
to
d64ff37
Compare
rwjblue
approved these changes
Aug 27, 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.
Speaking with the team, we would love to reach a 10 minute Commit -> CI
feedback loop goal. (Assuming the GH Actions queue depth isn't too deep)
We have spoken with GH to increase our concurrency, but in-order to
reach our goal each of our jobs cannot exceed 5->8minutes.
This is a first step in locking that in.
Note: I will wait until everyone is around to chat about this more.