ci: raise Windows checks timeout to 90 minutes#59647
Closed
efww wants to merge 1 commit intoopenclaw:mainfrom
Closed
ci: raise Windows checks timeout to 90 minutes#59647efww wants to merge 1 commit intoopenclaw:mainfrom
efww wants to merge 1 commit intoopenclaw:mainfrom
Conversation
Contributor
Greptile SummaryRaises the Confidence Score: 5/5
Reviews (1): Last reviewed commit: "ci: raise Windows checks timeout to 90 m..." | Re-trigger Greptile |
Author
|
Pre-existing flaky CI issue unrelated to my PR #58965. The same shard fails on origin/main. Closing this timeout workaround as it doesn't address the root cause. |
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.
Summary
Increase the
checks-windowsjob timeout from 60 minutes to 90 minutes.Why
PR #58965 hit a Windows-only timeout on
checks-windows-node-test-5even though the job made it all the way intoRun test (node)before GitHub cancelled it for exceeding the 1 hour cap.This does not look like a functional regression in the PR itself. It looks more like a CI stability issue where one Windows shard occasionally runs longer than the current budget.
Change
checks-windowstimeout-minutesfrom60to90Context
The failing run was:
GitHub reported:
The job has exceeded the maximum execution time of 1h0m0sNote
This is intentionally a small stabilization change. If the same shard keeps drifting upward, the better long-term follow-up would be to rebalance or further split the Windows test shards.