Enable more verbose logging

[goxberry]

As part of debugging some compiler flag settings, I'd like a command-line option to increase output verbosity to see what flags are being passed to the build systems spack is invoking during spack dev-build. If I were to file a PR adding a --verbose flag to uberenv, would that code be of interest?

Is there any roadmap for logging features in uberenv? I imagine there might be other phases of provisioning worth logging, but haven't yet reviewed the codebase with that thought in mind.

[white238]

Serac just noticed this change. This is a change in behavior in this commit: 8fb1aaa

I would like this able to be changed back with a quiet and/or verbose option. It is hard to track down differences in builds w/o running the whole build again.

[adrienbernede]

A more efficient strategy for debugging would be to directly relaunch the command as printed in the log, but remove the --quiet and possibly pass -v to spack, that way, one does not have to go through the preliminary stages (spack checkout, spack spec, etc).
I guess you are still interested in a --verbose flag for users not aware of the plethora of options in Spack ;)

[white238]

A more efficient strategy for debugging would be to directly relaunch the command as printed in the log, but remove the --quiet and possibly pass -v to spack, that way, one does not have to go through the preliminary stages (spack checkout, spack spec, etc).
I guess you are still interested in a --verbose flag for users not aware of the plethora of options in Spack ;)

Normally this would be fine (and what i do) but when we run TPL builds in docker containers, for example, I can't just restart the build because the docker container is reverted.

[adrienbernede]

Fair point ;)