Skip to content

api: make the four longest concurrent eval delays smaller - #240

Merged
zimbatm merged 1 commit into
mainfrom
test/concurrent-eval-speed
Oct 24, 2026
Merged

zimbatm merged 1 commit into
mainfrom
test/concurrent-eval-speed

Conversation

@zimbatm

@zimbatm zimbatm commented Oct 24, 2026

Copy link
Copy Markdown
Member

concurrent_eval_matches_sequential_eval took 89 to 263 s on the farm builders. It went past the 300 s nextest limit in builds 623, 627 and 628, so #236 and #237 left the merge queue.

Four cases still waited on slow 2000000 or slow 3000000: fn-identity, lint-speculated, lint-demanded and drv-speculated. They took 5 to 7 s each on an idle bld1. This PR sets them to 300000, the value that the route and ahead cases use (see #233).

On bld1 the test takes 3.2 s (it took 7.3 s before), and 19 s on 2 CPUs. It passed in 5 of 5 runs. No test or case is removed, and no timeout changes.

fn-identity, lint-speculated, lint-demanded and drv-speculated waited
on slow 2000000 or 3000000, and took 5 to 7 s each with 8 workers on an
idle builder. On a loaded farm builder the test took 89 to 263 s, and
it went past the 300 s limit in 3 of the last 11 builds.

300000 gives the helpers the same time to run ahead as in the route
and ahead cases. The test takes 3.2 s on bld1, down from 7.3 s.

Assisted-by: Claude Code (claude-opus-5)
Change-Id: I74a3e9aaba63d4f3fd7eb5b99f131850f57a47f1
@zimbatm
zimbatm enabled auto-merge October 24, 2026 01:15
@zimbatm
zimbatm added this pull request to the merge queue Oct 24, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Oct 24, 2026
@zimbatm
zimbatm added this pull request to the merge queue Oct 24, 2026
Merged via the queue into main with commit d29f9b3 Oct 24, 2026
5 checks passed
@zimbatm
zimbatm deleted the test/concurrent-eval-speed branch October 24, 2026 01:37
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