all-backend ledger: milestone-1 regen prune (torch 1684→ 1485, jax 335→ 292)#969
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## feat/backends #969 +/- ##
==============================================
Coverage 99.93% 99.93%
==============================================
Files 247 247
Lines 39375 39375
Branches 839 841 +2
==============================================
Hits 39350 39350
Misses 25 25 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
c262e99 to
0f681cc
Compare
…5->292) Milestone-1 ledger reconsideration (the policy's "major milestone where the ledger has permanently moved", not a per-integration regen). Source: regen run 27621760108 on regen/milestone-1-ledger (regen mode = no xfail applied, so every ledgered test runs for real; nothing is seed-skipped). The permanent move: #960's central coordinate coercion plus the landed P2.x potential and Pspecial migrations. Net (xfail): torch 1683->1484, jax 296->253; slow_skip held byte-identical (torch 1, jax 39) -> total torch 1684->1485, jax 335->292. Built from the full set of 13 jax + 13 torch regen fragments. One shard truncated at the 75-min session-timeout: jax test_SpiralArmsPotential / test_potential / test_scf / test_MultipoleExpansionPotential / test_snapshotpotential ran 259/410, so the 3 prior ledger entries among the 151 that did not run are carried forward (torch ran all 410 of that shard, so no torch carry-forward). Every other shard ran to completion and is applied in full. (History: an earlier revision of this commit built the ledger from only the first page of the run's 53 artifacts -- an unpaginated artifact listing -- which silently dropped ~11 shards' fragments and understated the ledger; rebuilt here from the complete fragment set.) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
0f681cc to
afa662e
Compare
All-backend test status (jax / torch)Commit Green is achieved via the checked-in xfail-ledger ( Overall: jax: 1326 passed · 250 xfail · 730 deferred | torch: 965 passed · 1488 xfail · 1 deferred Ledger size: 1737 entries (jax=253, torch=1484).
Per-shard counts
|
…5→ 292) (#969) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Restores the jax entry for this borderline FD-of-flow STM check that the #969 milestone-1 regen-prune erroneously dropped: the jax SpiralArms/ potential/scf shard truncated mid-run (issue #53), so this test was never re-run and its xfail entry was pruned away. Under jax the Multipole (non-axi) coefficients differ from numpy at the coefficient level, pushing this ~8e-4 FD-of-flow-vs-C-STM comparison just over the 5e-4 tolerance; numpy passes (verified), the C STM itself is correct. Tolerance unchanged. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Restores the jax entry for this borderline FD-of-flow STM check that the #969 milestone-1 regen-prune erroneously dropped (the jax SpiralArms/ potential/scf shard truncated mid-run, issue #53). Under jax the Multipole (non-axi) coefficients differ from numpy at the coefficient level, pushing this ~8e-4 FD-of-flow-vs-C-STM comparison just over the 5e-4 tolerance; numpy passes (verified), the C STM is correct. Not a #972 regression — this PR only adds C-STM autodiff files. Tolerance unchanged. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
…5→ 292) (#969) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
…5→ 292) (#969) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
…5→ 292) (#969) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
What
Milestone-1 reconsideration of the xfail-ledger (
tests/backend_xfail.txt) — the policy's "major milestone where the ledger has permanently moved significantly", not a per-#892-integration regen. Source: regen run 27621760108 onregen/milestone-1-ledger, built from the full 13 jax + 13 torch fragments.Burndown
backend_slow_skip.txtis byte-identical (deferred-slow tests are skipped in both modes, never regenerated — to be re-examined for vectorized entries at milestones).The permanent move that justifies the prune
One truncated shard (carry-forward)
The jax
test_SpiralArmsPotential/test_potential/test_scf/test_MultipoleExpansionPotential/test_snapshotpotentialshard hit the 75-min session-timeout (ran 259/410), so the 3 prior ledger entries among the 151 that didn't run are carried forward. torch ran all 410 of that shard, so no torch carry-forward. Every other shard ran to completion and is applied in full.Validation
CI on this PR re-runs the full all-backend matrix in normal mode (applies this ledger); any dropped test that regresses is caught here. (An earlier revision of this PR built the ledger from only the first page of the run's 53 artifacts — an unpaginated listing — which understated it; rebuilt from the complete fragment set.)
🤖 Generated with Claude Code