cabal-validate
: Better output verbosity defaults
#10573
Draft
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.
Closes #10569
Closes #10570
A new
--quiet
switch has been added, and some behavior in./validate.sh
(without--verbose
) has been moved into--quiet
mode:--hide-successes
will be passed to test suites in--quiet
mode, making it easier to track tests as they run--quiet
mode, making it easier to watchcabal build
and test suite outputSome output has been hidden unless
--verbose
is used:--verbose
is givenghc
andcabal-install
executables being used) and tool versions are not printed unless--verbose
is givenAdditionally,
print-config
,print-tool-versions
, andtime-summary
are no longer explicit steps, and are instead run implicitly. This means that./validate.sh -v -s build
will print the config and tool versions; they do not have to be listed explicitly.time-summary
is redundant in its current form and is removed. It may be added back in the future with more detailed output (e.g., which steps were run, how long did they take individually). (Partially closes #10571)