Repository navigation
release: pre-existing Linux parity failures block v0.5.1519 #8841
Description
Activity
Release candidate r16 surfaced one additional Linux parity mismatch before shard 8 hit its 150-minute timeout:
test_parcel_watcher_facade: Node exits inpackage_json_reader; Perry receives native events but times out waiting for the nested create event.
Evidence: https://github.com/PerryTS/perry/actions/runs/32922022811 (parity shard 8, 152/173 tests before timeout).
Tracked as a Linux
ci-envknown failure in #8846, which also moves parity from 8 to 12 shards and raises the timeout backstop so release-grade Full CI can complete.r17 Full CI surfaced one additional Linux parity blocker at exact candidate
b83a903e3084e449798127dfb8418a81b9e76b32:test_issue_4975_http_agent_keep_alive_connection_options: Node exits 0; Perry prints the expectedtrue/1250Agent connection options, then does not terminate and the harness kills it after 10s. This points to the keep-alive Agent/socket lifecycle afterserver.close(), not an output mismatch.
Run: https://github.com/PerryTS/perry/actions/runs/32935157745
Job: https://github.com/PerryTS/perry/actions/runs/32935157745/job/98076809981
Artifact: https://github.com/PerryTS/perry/actions/runs/32935157745/artifacts/9597975431The remaining r17 Full jobs were cancelled after the artifact was secured because the mandatory gate was already doomed. No publisher was dispatched; npm
0.5.1519and tagv0.5.1519remain absent.Acceptance: Perry must terminate with Node-equivalent lifecycle/output for this fixture; remove its Linux known-failure entry in the same PR.
Release candidate r18 (
d9d39a61973b659bae5b207abfb767ef012a1ebc) completed parity shard 8 tests, then the strict ratchet rejected two stale suppressions because both tests now pass on Linux:test_issue_806_curried_mixin_outer_capturetest_parity_stream
Evidence: run 32949659037, job 98120735010, artifact https://github.com/PerryTS/perry/actions/runs/32949659037/artifacts/9602879801
Cleanup PR: #8856
Release candidate r19 (
483e0515965b5eb5cb7f7c59e31f4e863cf26832) surfaced two mandatory blockers:- Cargo regression
issue_5247_value_call_source_location: both caught non-callable value-call cases aborted atjs_closure_unbox_callee_checkedbecause that throw-capable runtime boundary was stillextern "C"instead ofextern "C-unwind". - Linux parity
test_parity_native_value_profile: Perry emitted the newly intentionalpodCopy=7:9:513:-8field, while the checked-in expected output had not been refreshed.
Full run: https://github.com/PerryTS/perry/actions/runs/32967169957
Cargo job: https://github.com/PerryTS/perry/actions/runs/32967169957/job/98172243105
Parity job: https://github.com/PerryTS/perry/actions/runs/32967169957/job/98175183881
Parity artifact: https://github.com/PerryTS/perry/actions/runs/32967169957/artifacts/9612027399The remaining Full jobs were cancelled after both artifacts were secured. Simulator was green: https://github.com/PerryTS/perry/actions/runs/32967172848. No publisher was dispatched; npm
0.5.1519and tagv0.5.1519remain absent.- Cargo regression
- added 3 commits that reference this issue
on Aug 31, 2026
Release evidence
The mandatory Full CI for candidate 32cc6ea surfaced three Linux parity failures that are not currently tracked in test-parity/known_failures.json:
Full candidate run: https://github.com/PerryTS/perry/actions/runs/32898410858
Focused five-attempt controls show these predate the #8835 batch:
test_parcel_watcher_idle was also surfaced, but it is not a standalone parity program: it requires PERRY_WATCH_ROOT, PERRY_WATCH_READY, an external watcher package for Node, and an orchestrating harness. The release unblocker classifies it with a parity-skip header instead of recording a product bug here.
Acceptance criteria