cabal-validate: Some steps shouldn't be steps
#10570
Labels
cabal-validate
validate.sh (cabal-validate) test suite runner
meta: tracking
re: devx
Improving the cabal developer experience (internal issue)
type: testing
Issues about project test suites
Comments
9999years
added
meta: tracking
re: devx
This was referenced Nov 20, 2024
9999years
added a commit
to 9999years/cabal
that referenced
this issue
Nov 20, 2024
`print-config`, `print-tool-versions`, and `time-summary` are no longer explicit steps, and are instead run implicitly (closes haskell#10570). `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). `print-config` and `print-tool-versions` are hidden unless `--verbose` is given.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
print-config,print-tool-versions, andtime-summaryaren't really steps in the sense that they run commands with side-effects, they just print informative output for the user.There's two issues with this:
./validate.shwith no arguments clutters the output with a bunch of mostly-useless information../validate.sh -s cli-suite, configuration information and a summary of how long it took to run all the steps will be skipped.Proposal: Configuration information and a time summary should be displayed (or not displayed, depending on
--verbose) regardless of what steps are given.The text was updated successfully, but these errors were encountered: