scripts: Force verbose = true
#57
Conversation
#### Problem zx v8 suppresses output from subcommands, as outlined in the migration [guide](https://google.github.io/zx/migration-from-v7#migration-from-v7-to-v8). This makes it challenging to debug issues during CI or local runs. #### Summary of changes Set `$.verbose = true` via the utils script so that all jobs become verbose.
lorisleiva
left a comment
lorisleiva
left a comment
There was a problem hiding this comment.
I think this is okay but maybe it's worth setting it to:
$.verbose = !!process.env.CIIIRC the hyper-verbosity of v7 used to get quite annoying which is why they disabled it by default on v8.
|
Maybe I'm misunderstanding something -- why wouldn't we want output for CI? If a test fails in CI, and there's no output, then we won't have any information about the failure |
|
Oh sorry, |
|
Oh I see, I thought this was only needed for CI. Let's get this merged as-is on this repo and let me know if you're happy with the verbosity across all scripts. We may just need to quiet down some lower-level sub-commands here and there now. I think we can do this on a per-command basis with zx. |
2 participants
Problem
zx v8 suppresses output from subcommands, as outlined in the migration guide. This makes it challenging to debug issues during CI or local runs.
Summary of changes
Set
$.verbose = truevia the utils script so that all jobs become verbose.