Repository navigation
chore(ci): refresh the slow lane's weights from run 37598785795 - #260
Merged
Merged
Conversation
The table dated from run 37421410360 and part of 37449591693. Since then many slow tests were added (geometry harness cells, the coupling and nonlinear searches, REST oracles, sysid hunts) and were dealt by hash for want of a weight. Run 37598785795 (fa800c9, all 12 shards green) measured every file: the table now lists 211 files (185 before; 31 new, 5 dropped). Predicted test time per shard, on six: 71 to 79 minutes on jax 0.10.2 and 74 to 81 on jax 0.11.2. The old table, applied to the same measurements, would have put 56 to 96 and 69 to 89 minutes on the shards. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013UkCde7g23gTziUjYAvnKD
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
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.
Regenerates
tests/slow_lane_weights.jsonfrom the junit artefacts of the last full green slow-lane run, 37598785795 (commitfa800c98, all 12 shards green, 58 to 98 minutes per shard). The provenance names only this run, since it measured every file. The table now lists 211 files (185 before: 31 new, 5 dropped, the rest re-weighed).tests/usdwas measured but is a directory, not a file, and is left out by the tool. The prediction sentence indocs/developer_guide/testing_standards.mdmoves from "57 to 67" to "71 to 81" minutes. No change to the shard count, workflow,tests/_sharding.pyor any test; the previous weights commit did not touchCHANGELOG.md, so this one does not either.Predicted minutes of test time per shard (six weighted shards)
(Old-table rows: the old table's weights dealt with the tool's own
deal, files it did not list by path hash, loaded with this run's per-file measurements. This reproduces the 58 to 98 minute spread of the run.) The worst shard drops from 95.7 to 79.1 minutes (jax 0.10.2) and from 89.3 to 80.7 (jax 0.11.2), well under the 100-minute target.Heaviest files (minutes on jax 0.10.2, jax 0.11.2)
No file is near 45 minutes alone except
tests/property/test_sysid_truth_recovery.pyat 42.5 minutes on jax 0.11.2 (36.4 on 0.10.2); that is the floor on any shard's load, and it still leaves the worst shard at 80.7 minutes.Checked locally (collection and gates only; CI is the test run)
tests/compliance/test_ci_sharding.py: 63 passed (includes the guard that no table entry names a missing file and the 100-minute cap).scripts/check_*.pygates: exit 0.-m slow,MADDENING_TEST_SHARD=k/6:weighted: 115 + 404 + 376 + 161 + 212 + 389 = 1657, equal to the unsharded 1657 slow tests.🤖 Generated with Claude Code
https://claude.ai/code/session_013UkCde7g23gTziUjYAvnKD