alamb opened a new pull request, #2638: URL: https://github.com/apache/datafusion-sqlparser-rs/pull/2638
## Rationale for this change Same change as apache/datafusion#26293 (see apache/datafusion#26292 for background). The merge queue evicts PRs whose checks have not reported within 60 minutes (the GitHub default), even when nothing failed and the remaining jobs are only waiting for a runner. Each eviction discards CI that already passed, requires someone to re-queue the PR by hand, and reruns everything from scratch. This is now happening in this repo too, for example on #2626: https://github.com/apache/datafusion-sqlparser-rs/pull/2626#issuecomment-6175423847 All Apache projects share a GitHub runner queue, and it has been saturated for the last few days. ## What changes are included in this PR? Adds a `Merge Queue` ruleset to `.asf.yaml` that sets `check_response_timeout_minutes: 360`. Every other merge queue parameter is set to the value the queue has today (read back via the GraphQL API): `checkResponseTimeout: 3600, maximumEntriesToBuild: 5, maximumEntriesToMerge: 1, minimumEntriesToMerge: 1, minimumEntriesToMergeWaitTime: 300, mergeMethod: SQUASH, mergingStrategy: ALLGREEN`. ## What is the testing strategy for this PR? `asfyaml-validate` from apache/infrastructure-asfyaml reports the file as valid. After merge, `checkResponseTimeout` in the GraphQL query below should read `21600` instead of `3600`, and `gh api repos/apache/datafusion-sqlparser-rs/rulesets` should list a `Merge Queue` ruleset. ``` gh api graphql -f query='{ repository(owner:"apache", name:"datafusion-sqlparser-rs") { mergeQueue(branch:"main") { configuration { checkResponseTimeout } } } }' ``` ## Are there any user-facing changes? No. Written with assistance from Claude Code. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
