Menu ▾ ▴

#1717 ci(tests): re-measure harness weights so core pristine shard 6 fits its cap again (DIVE-8749)

closed
nobody
None
2 days ago
2 days ago
Anonymous
No

Originally created by: lodar

Fixes main red: unit-tests core-pristine-confirm (6) + test-confirm @6e1e2516 (run 44421508722), exit 4 with 119/119 harnesses green. Budget red, not a test failure.

Cause: not [#1712] (it touches model names and two tests on other shards). Shard 6 was already 330s on its first box at the previous green sha a96434f5 (run 44298553604); that run passed only because the confirm box drew 296s. This time the confirm box drew 331s against a 309s effective cap. The 2026-11-13 weights table had drifted: the planner loaded shards 6 and 1 (327s / 299s) and left shards 2 and 4 near 220s.

Fix: ran scripts/refresh-harness-weights.sh (core run 44298553604, full run 44298553674) and regenerated tests/lib/harness-weights.tsv. Added changelog.d/DIVE-8749.md. No cap, shard count or harness changed.

Check: tier.sh list core | tier.sh shard 6 <env> <tsv> (709 core harnesses, 0 unpriced), each plan priced at the red run's own per-file times from its shard report artifacts:

  • old table, pristine: 299 / 225 / 262 / 219 / 266 / 327s. Matches the red run's actual wall-clock (300/226/263/220/267/328) to the second.
  • new table, pristine: 278 / 269 / 274 / 256 / 255 / 266s (worst 93% of the raw cap)
  • old table, installed: 384 / 272 / 271 / 316 / 230 / 393s. New: 341 / 288 / 303 / 313 / 318 / 301s.

Residual: pristine core is 1598s over 6 shards, about 89% of capacity on average, so this buys days, not weeks. Installed-host passes only through runner calibration. The next heavy harness reds again whatever the table says; that is a merge/retire/shard decision this PR does not make.

🤖 Generated with Claude Code

Related

Tickets: #1712

Discussion

  • Anonymous

    Anonymous - 2 days ago

    Originally posted by: lodar

    Superseded by [#1718] (DIVE-8748, graded PASS at fbabb127): same harness-weights regen. Closing to avoid a conflict race.

     

    Related

    Tickets: #1718

  • Anonymous

    Anonymous - 2 days ago

    Ticket changed by: lodar

    • status: open --> closed
     

Log in to post a comment.