ci(memory): restore 290/315 MB json_churn ceiling reverted by #1324 - #1422
Merged
Conversation
PR #1324 ("Port GC checkpoint runtime work for #1090", e933b89) reverted the 290/315 MB ceiling from v0.5.1022 (#1286 / 4fcfddb) back to 250/275 while rewriting the surrounding comments. The v0.5.1024 release-packages compile-smoke job then hit the same Ubuntu overrun we already fixed once: default 268 MB / limit 250 MB (+7%) gen-gc-explicit 268 MB / limit 250 MB (+7%) force-evac+verify 288 MB / limit 275 MB (+5%) Restore the wider ceiling and replace the comment with one that references the actual rebump history (v0.5.1024 measurements + the #1324 revert) so the next contributor doesn't accidentally undo it again. Production binaries are stripped by the linker; these RSS figures are unstripped release-build artefacts used as a regression signal, not a deployment-size measurement. Refs #1090 #1286 #1324.
Merged
4 tasks
proggeramlug
added a commit
that referenced
this pull request
May 22, 2026
…arity skip-list + bump (#1426) Unblocks the v0.5.1024 release-packages gate (run #26298996134 + simctl run #26298996081): - **simctl iOS**: `find_geisterhand_lib` fell back to host `target/release/<lib>.a` when the cross-target `.a` was missing, feeding the linker a macOS `.a` against an iOS-sim target. The same fallback masked the auto-build trigger in `link/mod.rs` so the cross-target geisterhand libs never got built. Fix: when a target triple is specified, search only the triple's release directories and skip host fallbacks. Host build (target = None) path unchanged. - **parity** (2 NEW failures triaged): - **#1423** `test_async_local_storage_context` — `.enterWith` / `.exit` not implemented end-to-end (sibling slice of #788 #789). - **#1424** `test_json_lazy_reviver` — `JSON.parse(blob, reviver)` on a lazy-tape top-level array exits before any `console.log` fires. Likely GC checkpoint / copied-minor fallout. Both added to `known_failures.json` under `bug-open` with the new issue numbers per feedback_granular_gap_issues.md. - **compile-smoke memory ceiling** restore (PR #1422 / dec43e2) is already on main; CHANGELOG entry calls it out for completeness. Closes the v0.5.1024 release-packages failure; tagging v0.5.1025 should land cleanly.
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
1 participant
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.
Summary
Test plan
cargo fmt --all -- --checkcleanRefs #1090 #1286 #1324.