Repository navigation
Conversation
andreaTP
force-pushed
the
corpus-command-harness
branch
from
October 27, 2026 18:10
a144cfb to
e999b59
Compare
andreaTP
marked this pull request as ready for review
October 28, 2026 12:45
Contributor
Author
|
This is now ready for review 🙏 |
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.
Runs every Rust command program from the component corpus through
WasiPreview2and checks its exit code, stdout and stderr against the spec beside it. Each spec was recorded by running its program on wasmtime with the corpus'sverify.sh, so a pass means the same result wasmtime gave.All 11 programs pass: hello, args, env, exiting with success and with failure, an empty stdin, file read/write, directory listing, random and clocks. This is the first time real
wasm32-wasip2programs built by a stock Rust toolchain run end to end on endive-cm.The spec format has no field for stdin, so stdin is always empty. Rust's standard library only reports success or failure, so the exit codes checked are 0 and 1.
CorpusCommandTestmirrors Endive's WASI test runner:rootfixture into an in-memory ZeroFS preopened as/;[name, args...]andenv;run, and compares the exit code and output.The programs rely on the corpus (#71), wasi:cli (#70) and version-compatible linking (#69), since they import
@0.2.6. All three are onmain, so this is now the single test commit on top.