Skip to content

ci(TC-2917): more time for the cold DuckDB test leg - #598

Merged
samgbafa merged 2 commits into
mainfrom
skgbafa/tc-2917-ci-duckdb-node-timeout
Nov 13, 2026
Merged

samgbafa merged 2 commits into
mainfrom
skgbafa/tc-2917-ci-duckdb-node-timeout

Conversation

@samgbafa

@samgbafa samgbafa commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

CI-only change for TC-2917. No product code changes.

The DuckDB leg's step Run DuckDB policy and request telemetry through node binaries rebuilds bundled DuckDB for the node feature graph. On a cold cache that build took about 14.5 minutes on #582 (run 43477627045), so the 15-minute step cap stopped it while its tests were running; no test had failed. #591 hit the same timeout twice.

  • That step's timeout goes from 15 to 25 minutes.
  • The test job's timeout goes from 45 to 60 minutes, so a cold run of the 20-minute core step, the 25-minute node step and setup fits inside it. The cap applies to every leg of the test matrix.

No tests are removed or changed.

A cold bundled DuckDB compile for the node feature graph took about
14.5 minutes on PR #582, so the 15-minute cap stopped the step while
its tests were running. 25 minutes still fits the job's 45-minute cap.
On a cold build the 20-minute DuckDB core step, the 25-minute node
step and setup can exceed the old 45-minute job cap.
@samgbafa samgbafa changed the title ci(TC-2917): allow 25 minutes for the DuckDB node-binaries step ci(TC-2917): more time for the cold DuckDB test leg Nov 13, 2026
@samgbafa
samgbafa merged commit d6e4c96 into main Nov 13, 2026
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant