python: Raise test pipeline provisioning timeout to 300s - #6835
Merged
Conversation
The arm64 CI workload tests hit the 180s deadline when parallel test workers request several fresh nodes at once (node boot plus image pull). The failed runs' cleanup found the pipelines provisioned shortly after the deadline, so the timeout was too tight rather than provisioning broken. Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
mihaibudiu
approved these changes
Aug 10, 2026
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
2 participants
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.
Raises the shared test harness provisioning timeout in
build_pipeline()from 180s to 300s.Why: in ci.yml run 31395130678 (attempt 3), three arm64 workload tests (
test_constant_table,test_now,test_aggregate_joins) failed with "Pipeline could not be provisioned within the timeout of 180s". The job's cleanup step then found all three pipelines alive and reclaimed them: they provisioned shortly after the deadline. The workload suite launches several pipelines at once via pytest-xdist, so multiple pods race for fresh arm64 nodes and the 180s budget does not cover node boot plus the image pull.Genuine provisioning breakage now takes 2 minutes longer to surface per test; workers run in parallel, so wall-clock cost on a green run is zero.