Repository navigation
fix(ci): raise merge queue timeout - #9096
Conversation
If this limit is too low, the merge queue can enter a starvation loop where every job times out if runners are simply busy. Raising the limit stops this.
Automated Reviewer SuggestionsBased on the
|
There was a problem hiding this comment.
LGTM!
We need to find a way to merge #9064 first.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9096 +/- ##
=========================================
Coverage 92.33% 92.33%
Complexity 5045 5045
=========================================
Files 1261 1261
Lines 54120 54120
Branches 6768 6768
=========================================
Hits 49973 49973
Misses 2486 2486
Partials 1661 1661
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
@parshimers do you have permission to force merge this one? I don't think we can merge any PR without this. |
|
@parshimers I combined this with #9064 in #9100 — your commit is cherry-picked as-is (authorship kept), since this PR can't pass the Scala checks without the setup-sbt bump. #9100's own merge group still runs under the 45-minute limit until the |
|
Sounds good. I do think we have to do something to force it in assuming the runner starvation stays like this for any longer. I am talking with infra about it. Either I might be given permission to, or they may do it for us. |
What changes were proposed in this PR?
If this limit is too low, the merge queue can enter a starvation loop where every job times out if runners are simply busy. Raising the limit stops this.
Any related issues, documentation, discussions?
Closes #9095 and https://issues.apache.org/jira/browse/INFRA-28569
How was this PR tested?
It wasn't; it's specific to ASF infra. I got the idea from a helpful hint from Andrew Lamb of DataFusion.
Was this PR authored or co-authored using generative AI tooling?
No