Repository navigation
Build and test from a fresh clone on Zig 0.16 - #48
Merged
Merged
Conversation
The workspace build.zig defined test-core, test-all and test-frontier but no `test` step, so `zig build test` failed with "no step named 'test'". Add `test` as the aggregate of test-core and test-all (the in-process unit suites). test-frontier stays separate: it shells out to jq, python3 and nested builds. Record measured test counts in README and PLATFORM.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Root cause
The workspace
build.zigdefinestest-core,test-allandtest-frontier, but noteststep, sozig build teston a fresh clone fails witherror: no step named 'test'. The code and tests themselves already build and pass on Zig 0.16.0.Fix
Add a
teststep that depends ontest-coreandtest-all(the in-process unit suites).test-frontieris still a separate step because it shells out tojq,python3and nestedzig buildruns. README now listszig build test, and thetest-corecount in PLATFORM.md is updated from 75 to the measured 159.Before / after (fresh clone, Zig 0.16.0, macOS arm64)
zig build test --summary all→error: no step named 'test'(no Build Summary)Build Summary: 186/186 steps succeeded; 1688/1688 tests passedzig build --summary all:Build Summary: 1/1 steps succeededNote (not changed here):
zig build test-frontierfails on macOS becausearena/scripts/verify.shuses GNU-stylesed -i 's/…/…/' file, which BSD sed rejects (invalid command code f).🤖 Generated with Claude Code