feat: nargo test -q (or nargo test --format terse)
#6776
Conversation
This file contains 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
Co-authored-by: Tom French <[email protected]>
It seems `max_num_threads` is how many threads in theory Rayon could spawn, which was 2**16 on my machine. `current_num_threads` is the recommended number of threads to use, which is 10 on my machine.
Compilation Sample
|
Peak Memory Sample
|
asterite
force-pushed
the
ab/nargo-test-machine-readable-output
branch
from
a4d7df8 to
94aabde
Compare
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.
Descriptio
Made on top of #6728
Problem
Towards #6733
Summary
Eventually we'll have
nargo test --format json, which is what #6733. As a first step I wanted to introduce theformatflag and, to try that abstraction in code I introduced a terse formatter similar to Rust.On failure we don't immediately print the error. Instead, it's printed at the end (like in Rust). I can imagine this could be used in CI to reduce the output verboseness, because I guess all that matters in CI is seeing which tests failed.
Like in Rust, there are two ways to trigger this terse behavior:
-q(or--quiet) or--format terse. We could just keep--format tersebut I think-qis convenient (andformatis more general as it will soon supportjson).Here's the output when all tests pass:
Additional Context
It would be nice to get rid of those "proptest" messages but I don't know why they happen.
Documentation
Check one:
PR Checklist
cargo fmton default settings.