Skip to content

fix(ci): move Test + Clippy back to ubuntu-latest (unblocks all open PRs)#102

Merged
avrabe merged 1 commit into
mainfrom
fix/ci-runner-disk-space
May 11, 2026
Merged

fix(ci): move Test + Clippy back to ubuntu-latest (unblocks all open PRs)#102
avrabe merged 1 commit into
mainfrom
fix/ci-runner-disk-space

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented May 11, 2026

Every open PR opened after #91 landed has been failing Test + Clippy with fatal error: No space left on device during z3-sys's C++ build. Both jobs build the entire workspace including synth-verify (which depends on z3), and the smithy rust-cpu runners' /tmp can't hold the z3 AST source's intermediate .s files.

This reverts just those two jobs back to ubuntu-latest. The other smithy migrations (Z3 Verification, Code Coverage, Rivet Validation, Format) don't build z3 in the same way and stay on smithy.

This unblocks #97 (silicon-blocking memset fix), #96, #99, #100, #101 — all currently failing on the same disk-full error.

Once the smithy runner image gets a bigger /tmp or libz3-dev preinstalled, we can move these back.

The smithy migration in #91 moved Test and Clippy to self-hosted rust-cpu
runners. Both jobs build the entire workspace including synth-verify,
which depends on z3-sys — a large C++ compile that fills the smithy
runners' /tmp during code generation ("fatal error: No space left on
device" on roughly half the z3 AST source files).

Every PR opened after #91 landed has been hitting this. Reverting these
two jobs to ubuntu-latest (which has ~14 GB /tmp) unblocks every open PR.
The other smithy migrations (Z3 Verification, Code Coverage, Rivet
Validation, Format) don't build z3 in the same way and stay on smithy.

Once the smithy runner image gets a bigger /tmp partition (or libz3-dev
preinstalled so z3-sys uses the system lib), move them back.
@codecov
Copy link
Copy Markdown

codecov Bot commented May 11, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@avrabe avrabe merged commit 6febcbe into main May 11, 2026
8 of 9 checks passed
@avrabe avrabe deleted the fix/ci-runner-disk-space branch May 11, 2026 05:21
avrabe added a commit that referenced this pull request May 11, 2026
…x-M (#97)

Closes #93 (silicon-blocking).

Root cause: `optimizer_bridge::wasm_to_ir` had no handler for `I64ExtendI32U` / `I64ExtendI32S` / `I32WrapI64` — they fell through to `Opcode::Nop`, leaving their result vregs unmapped. The downstream `get_arm_reg` silent R0 fallback caused subsequent i64 shifts to read R0 as their `rm_lo`/`rm_hi` — destroying memset's destination pointer on real silicon.

Fix: add the three missing op handlers in wasm_to_ir + ir_to_arm + analyze_i64_local_gets. 5 regression tests added (3 fail-before-pass-after).

Format + Rivet failures are smithy-runner crashes (BlobNotFound on logs — same as #102's pattern). Every functional gate passes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant