Repository navigation
ci: reduce sanitizer debug info footprint - #765
luisleo526 wants to merge 2 commits into
Conversation
Use GCC minimal debug information for instrumented Debug profiles while retaining file and line data, sanitizer flags and the full test selection. Keep the definition below the cited profile-floor table so existing documentation anchors remain valid. This is a measurement step: it lowers debug info only. The pass condition is at least 20 GB free after Verify on the worst hosted sanitizer shard. If that margin is not reached, each shard will build only its own targets next.
![graphify-labs[bot]](https://avatars.githubusercontent.com/in/4356270?s=60&v=4){kind=small}
There was a problem hiding this comment.
Graphify reviewed this change.
No issues found by static checks — no coupling regressions or blocking issues in the code graph. That is not the same as safe to merge: see what was not checked.
Not checked: tests were not run; formal verification proved 0 of 1 changed function(s) (1 not verified).
Formal verification. PR-changed functions: 0/1 verified (0 proven, 0 may-equivalent, 0 distinguished) · 1 not verified (1 unsupported).
Not verified on this run: cmake\_cache\_definitions (unsupported).
Graphify review — findings
Adds -g1 (compact line-table debug info) to CMAKE_C_FLAGS_DEBUG and CMAKE_CXX_FLAGS_DEBUG for the sanitizers and live-sanitizers profiles in cmake_cache_definitions, so the full shard population compiles with a much smaller object/debug footprint. Hosted sanitizer runners hit about 5MB free disk on the last main run with ordinary Debug DWARF. Sanitizer flags, source/test population, and shard selection stay the same, and other profiles are unaffected. Tests now check that both profiles emit the flags, and that the sanitizers profile passes them in the configure argv.
No blocking issues surfaced.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 615 functions depend on the 570 functions this change touches.
Health — grade B; 5 existing hotspot(s) in the area this change touches (pre-existing, not introduced here):
check_commands()— 22 callers, 5 callees (high)validate_config()— 24 callers, 4 callees (high)main()— 1 callers, 13 callees (high)archive_inputs()— 1 callers, 6 callees (medium)validate_ctest_shard_union()— 0 callers, 7 callees (medium)
Verification — 615 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 598 function(s) in the blast radius were not formally verified this run
Formal verification
Could not verify: Could not verify cmake\_cache\_definitions.
The verifier did not have enough to check cmake\_cache\_definitions, so it is saying so rather than guessing. No false assurance is the whole point.
Guarantee: No guarantee either way, this is an honest abstention, not a pass.
Note: Reason: parameter `cfg` is annotated `VerifyConfig` — outside the synthesizable primitive/collection set
…es starts (#766) Add the run option series_origin_ms, which declares where the reference series starts, so EMA warm-up can match a reference that begins at the start of the range. live-sanitizers not measured on this head: hosted disk exhaustion, same as main c9a6414; covered by the first main sanitizer run after #765.
…in the same execution (#769) Merge gate on head 894bf4f: the required CI result, the corpus parity check and the review all pass. live-sanitizers and the derived native-live-gate are red on runner disk (No space left on device), the same as main b09f79d; fixed by #765. The sanitizer shards fail the same way on both. This change does not cause them. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Merge gate on head 14d7d9b: the required CI result, the corpus parity check and the review all pass. In the post-merge native run on the same tree, every native shard and live-tsan pass. live-sanitizers, the derived native-live-gate and the sanitizer shards are red on runner disk (No space left on device), the same jobs that fail on main 06eb496; #765 addresses it. This change does not cause them. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Combine six engine pull requests into one change, gated once. Source pull requests and the heads merged here: - #774 Add live drawing capacity to the runtime limit vocabulary (99b0bfe) - #764 Preserve direction in trade size accessors (834333f) - #765 ci: reduce sanitizer debug info footprint (be68cab) - #773 Include ABI layout probe in PR smoke (4f31c10) - #772 ci: promote the engine baseline on parity alone (349418e) - #759 Write bounded drawing arenas in place and share their slots between checkpoints (cecedc0) Gate on head b4c316b (tree 1a4b2ea): required CI green; one parity sweep over 7,989 probes with no lost coverage, no band movement and no hard regression; one review of the combined diff. In the post-merge native run on the same tree, every native shard and the thread-sanitizer leg pass; the address-sanitizer legs fail on runner disk space (No space left on device), the same jobs that fail on main. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Summary
Hosted sanitizer shards run short of disk space during the Debug build. This change uses GCC minimal debug information (
-g1) for thesanitizersandlive-sanitizersprofiles only. File and line data in sanitizer reports stay intact; sanitizer flags, test selection, shard layout, runners and timeouts are unchanged.live-tsanis not touched.The definition sits below the cited profile-floor table in
scripts/ci_verify.py, so existing documentation anchors stay valid.Measurement step
This lowers debug info only. The pass condition is at least 20 GB free after Verify on the worst hosted sanitizer shard, measured on the main run after merge. If that margin is not reached, the next step is for each shard to build only its own targets.
Tests
scripts/test_ci_verify.pygains assertions that both profiles carry-g1; the full reader passed on this exact head.🤖 Generated with Claude Code