ci: migrate 9 of 12 workflow jobs to smithy self-hosted runners#134
Merged
Conversation
rust-cpu test, coverage, clippy, bench-smoke, update-fixtures,
fuzz-smoke, release build (x86_64-linux)
light fmt, release publish
Stays on hosted (release.yml matrix):
- build aarch64-linux uses `cross` (Docker container; podman compat untested)
- build x86_64-darwin macOS only on GitHub-hosted
- build aarch64-darwin macOS only on GitHub-hosted
No special workarounds needed: every migrated job is a clean
cargo build/test/clippy/fmt on Linux with no sudo, apt-get, or
container directive. wasm32-wasip2 used by fixtures.yml is
pre-installed on smithy. Nightly Rust used by fuzz-smoke is
available via rustup.
cargo-fuzz builds with --target x86_64-unknown-linux-musl by default on Linux. GitHub-hosted runners ship the musl std target preinstalled; smithy's nightly install does not, so the build fails with `can't find crate for std` for x86_64-unknown-linux-musl. Add an explicit targets line to the dtolnay/rust-toolchain step so rustup pulls the musl std for nightly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 10, 2026
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
Migrates meld's CI from GitHub-hosted to the pulseengine smithy
self-hosted fleet, following the playbook proven on spar (#201),
rivet (#262), kiln (#247), and gale (#35). Nine of twelve jobs
move; the three that stay are constrained by toolchain or OS.
meld is a WebAssembly component fusion tool. wasm32-wasip2 (used
by
fixtures.yml) and nightly Rust (used byfuzz-smoke) are bothpre-installed on smithy via rustup, so no extra setup is needed.
Migrated -> smithy
rust-cpurust-cpurust-cpulightrust-cpurust-cpurust-cpurust-cpulightlightfor fmt + release-publish (no compile work). All compile-boundjobs go to
rust-cpu(12 G MemoryHigh, plenty for cargo work).Stays on hosted (release.yml matrix)
aarch64-unknown-linux-gnucrosswhich launches a Docker container; podman-docker compat shim on smithy is untested for cross imagesx86_64-apple-darwinaarch64-apple-darwinIn-place comments above each kept-hosted matrix entry capture the reason.
Workarounds applied
None. Every migrated job is a clean cargo build/test/clippy/fmt on
Linux with no sudo, apt-get, or container directive.
actions-rs/toolchainand
dtolnay/rust-toolchainboth no-op cleanly when rustup is alreadypresent on PATH.
Expected win
Same shape as the prior migrations: queue elimination on the org-free
Actions tier dominates total wall time. fuzz-smoke's 4-target matrix
and the test/coverage/clippy trio are the largest individual wins.
Test plan
journalctl -u smithy-trace-eacces.serviceRollback
Revert this commit; all
runs-on:entries flip back toubuntu-latestand the release matrix returns to its prior shape.