ci: increase "gclient sync" output timeout #40963
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
VerteDinde
added
fast-track 🚅
codebytere
approved these changes
Jan 11, 2024
|
No Release Notes |
VerteDinde
added a commit
that referenced
this pull request
Jan 11, 2024
This reverts commit be4eb4e.
VerteDinde
added a commit
that referenced
this pull request
Jan 11, 2024
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.
Description of Change
#40953 removed the git cache from the gclient sync step, which may be causing release builds to timeout. Rather than adding it back it, let's increase the gclient sync step output timeout limit to allow a new cache (minus git cache) to be built. Then we can compare the total build numbers and see what the differences are.
Checklist
npm testpassesRelease Notes
Notes: none