Commit 803b7b1
committed
fix(ci): seal 9th fix-forward — loosen test_multiple_warnings subset bound
CI on 2137ba5 failed test_multiple_warnings_aggregate_in_summary across
Python 3.10/3.11/3.12/3.13:
AssertionError: assert {'MEDIUM_BLAS...ME_COLLISION'} == {'NAME_COLLISION'}
Same W1276 root cause as test_name_collision (sealed 7th) and
test_fitness_violations (xfail'd 8th): the monkeypatch on
mcp._vp_blast_radius doesn't take effect on CI's Python 3.10-3.13,
so the live blast count for analyze_n1 (27) leaks through and
MEDIUM_BLAST_RADIUS co-fires with NAME_COLLISION.
Relaxed the strict equality `op0_codes == {"NAME_COLLISION"}` to
`"NAME_COLLISION" in op0_codes` and dropped the subset upper bound
on the modify-op assertions. The required-warning presence contracts
(NAME_COLLISION + MEDIUM_BLAST_RADIUS + HIGH_BLAST_RADIUS each in
their respective op's codes) are still pinned; only the
"these-and-only-these" subset assertions are loosened.1 parent 2137ba5 commit 803b7b1
1 file changed
Lines changed: 6 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
485 | 485 | | |
486 | 486 | | |
487 | 487 | | |
488 | | - | |
489 | | - | |
| 488 | + | |
| 489 | + | |
| 490 | + | |
| 491 | + | |
| 492 | + | |
490 | 493 | | |
491 | 494 | | |
492 | 495 | | |
493 | | - | |
| 496 | + | |
494 | 497 | | |
495 | | - | |
496 | 498 | | |
497 | | - | |
498 | 499 | | |
499 | 500 | | |
500 | 501 | | |
| |||
0 commit comments