Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions

wai-conformance: two arm64-heavy jobs build without debuginfo (the VM's disk filled mid-link) #553

Merged
dcharlot merged 1 commit from ci/arm64-no-debuginfo into main 2026-10-31 06:10:11 -04:00
Conversation 0 Commits 1 Files changed 1 +10
dcharlot commented 2026-10-31 04:00:38 -04:00
Owner
Copy link

Why

The linux-arm64 runner's VM has a 196 GB data disk. Three WAI conformance jobs at once filled it, and a link failed with No space left on device:

  • #542, once;
  • #550, twice: cargo-class corpora · linux-arm64 and independent verifiers (Python), both at 07:34 UTC on 2026-10-31.

Each such job holds about 54 GB of debug targets. Most of that is DWARF, which nothing in CI reads.

What

CARGO_PROFILE_DEV_DEBUG: '0' at job level for cargo-classes (all three legs) and independent-verifiers. Each gets a comment saying why.

  • Panic messages keep their file:line, which comes from the panic location, not from DWARF.
  • The precedent is standards-build.yml's trim of jouleclaw-rs. It went to about 6 GB without debuginfo, and the whole suite still passed.
  • The first run of each leg rebuilds without debuginfo; later runs build incrementally as before.

No code change.

🤖 Generated with Claude Code

## Why The linux-arm64 runner's VM has a 196 GB data disk. Three WAI conformance jobs at once filled it, and a link failed with `No space left on device`: - #542, once; - #550, twice: `cargo-class corpora · linux-arm64` and `independent verifiers` (Python), both at 07:34 UTC on 2026-10-31. Each such job holds about 54 GB of debug targets. Most of that is DWARF, which nothing in CI reads. ## What `CARGO_PROFILE_DEV_DEBUG: '0'` at job level for `cargo-classes` (all three legs) and `independent-verifiers`. Each gets a comment saying why. - **Panic messages keep their file:line**, which comes from the panic location, not from DWARF. - **The precedent is `standards-build.yml`'s trim of jouleclaw-rs.** It went to about 6 GB without debuginfo, and the whole suite still passed. - **The first run of each leg rebuilds** without debuginfo; later runs build incrementally as before. No code change. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
wai-conformance: the cargo-class corpora and the independent verifiers build without debuginfo
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 13s
Details
standards workspaces build + test / macOS energy backends (pull_request) Has been skipped
Details
WAI conformance / does this change touch it (pull_request) Successful in 5s
Details
WAI conformance / cross-arch byte-equality · linux (pull_request) Successful in 39s
Details
WAI conformance / cross-arch byte-equality · macos (pull_request) Successful in 52s
Details
WAI conformance / faces from keypoints under wasm32-wasip2 (wasmtime) (pull_request) Successful in 1m46s
Details
WAI conformance / codec wrappers · fuzz smoke, text decode limits, C entry points, provenance, the semantic path (pull_request) Successful in 1m53s
Details
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 3m22s
Details
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 15s
Details
WAI conformance / fast integer kernels, every x86_64 kernel set (AVX-512 silicon) (pull_request) Successful in 2m53s
Details
WAI conformance / quantum core and corpus under wasm32-wasip2 (wasmtime) (pull_request) Successful in 3m12s
Details
WAI conformance / cargo-class corpora · linux (pull_request) Successful in 14m37s
Details
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 19m34s
Details
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 22m33s
Details
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 50s
Details
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 15m58s
Details
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 33s
Details
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 1m56s
Details
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 1h2m10s
Details
39e3d79056 
Three of these jobs at once on the linux-arm64 VM's 196 GB data disk ran out of
space mid-link ("No space left on device"): #542, and twice on #550. Nothing in CI
reads DWARF, and it is most of a debug target's size; panic messages keep their
file:line, which comes from the panic location. standards-build.yml already trims
jouleclaw-rs the same way (~6 GB without debuginfo).

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Transaction-Science/open-standards!553
No description provided.