ci: migrate fuzz-smoke (12 targets) + sanitizers (3 modes) to smithy#35
Open
ci: migrate fuzz-smoke (12 targets) + sanitizers (3 modes) to smithy#35
Conversation
First pass for gale, conservative subset of two container-free
workflows (no sudo / no apt-get / no container: directive) that
mirror the spar/rivet/kiln pattern:
rust-cpu fuzz-smoke.yml 12-target matrix, 60s each
rust-cpu sanitizers.yml ASan / TSan / LSan, nightly Rust
Stays on hosted (out of scope for this PR):
- bazel-tests + 5 engine-bench-* + coverage + llvm-lto + nightly
+ renode-tests + zephyr-tests
All use container: directive with vendor CI images. Smithy has
podman-docker compat shim but it is UNTESTED on these images;
keep on hosted until validated separately.
- formal-verification (verus / kani / rocq)
verus + rocq go through Bazel + Nix which smithy doesn't ship.
kani bundles CBMC (~100 MB), not pre-installed on smithy.
4 tasks
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
First gale pass onto smithy self-hosted, deliberately small. Two
workflows whose steps are container-free and don't need any host
tooling smithy doesn't already ship:
fuzz-smoke.yml— 12-target matrix, 60s per targetsanitizers.yml— ASan / TSan / LSan, nightly Rust + rust-srcBoth move to the
rust-cpuclass (12 G MemoryHigh, sccachedisabled today, plenty of compile capacity).
Out of scope this PR (each gale workflow listed once for clarity)
bazel-testscoverageengine-bench-*(5 files)formal-verification(verus/kani/rocq)llvm-ltonightlyrenode-testszephyr-testsThe container: jobs are migrable via smithy's podman-docker compat
shim, but UNTESTED on these specific Zephyr / vendor images. Belongs
in a follow-up PR with a controlled validation, not a "flip + hope"
move.
Expected win
Same as spar / rivet / kiln: queue elimination on the org-free
Actions tier dominates. fuzz-smoke and sanitizers both run real
nightly cargo work for minutes-scale, exactly the shape that
exposes runner queue waste.
Test plan
rust-cpuand finish greenrust-cpuand finish greenjournalctl -u smithy-trace-eacces.serviceRollback
Revert this commit; both workflows flip back to
ubuntu-22.04.