Repository navigation
release blocker: Any callback entry resolution aborts moving-GC packed-loop fixture #9119
Closed as not planned
Description
Summary
Commit 1908269 (#9109) makes the issue_8690 moving-GC regression fixture abort deterministically. The immediately preceding release candidate f9d0178 passes the same test.
Exact failing test
RUST_TEST_THREADS=1 cargo test -p perry --test issue_8690_loop_versioned_arraylike mutations_and_moving_gc_resume_with_generic_semantics -- --exact --nocapture
Observed output
The compiled fixture prints:
break=31
declared-string=7
It then aborts with status 134 from a non-unwinding panic before completing the remaining mutation cases.
Release impact
This blocks v0.5.1519. The release branch should temporarily revert #9109 while preserving it in ancestry. A follow-up fix must restore Any-typed callback entry resolution without breaking the moving-GC packed-loop fixture.
Acceptance criteria
- The exact issue_8690 test passes with moving GC.
- Existing perf(codegen): entry resolution reaches Any-typed callback params — __commonJS-shape calls 7.4 → 4.5 ns (typed parity) #9109 callback-entry-resolution coverage remains green or is replaced by a safe guarded implementation.
- Full CI and simulator parity pass.
Activity
proggeramlug commentedon Aug 30, 2026
Closing as invalid test setup. The abort was reproduced only when the integration test linked the debug runtime. The earlier green run inherited PERRY_RUNTIME_DIR pointing at the matching release runtime; the later command omitted it. The temporary release-branch revert was not pushed and has been undone. Validation is continuing with a commit-matched release compiler/runtime.
fix(codegen): defer Any callback entry resolution (#9119)
fix(codegen): restore Any callback entry resolution (#9119)