diff options
| author | Harmen Stoppels <harmenstoppels@gmail.com> | 2022-10-24 03:12:38 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-23 18:12:38 -0700 |
| commit | 7d99fbcafd4720babe2a0d325df099ed9056f5e1 (patch) | |
| tree | e369403ebb5808e3984db5c23fbf8b8fd1edfb2f /COPYRIGHT | |
| parent | 6c32c6fbdba52109de9f112dfe785c66b7d114e8 (diff) | |
| download | spack-7d99fbcafd4720babe2a0d325df099ed9056f5e1.tar.gz spack-7d99fbcafd4720babe2a0d325df099ed9056f5e1.tar.bz2 spack-7d99fbcafd4720babe2a0d325df099ed9056f5e1.tar.xz spack-7d99fbcafd4720babe2a0d325df099ed9056f5e1.zip | |
backtraces with --backtrace (#33478)
* backtraces without --debug
Currently `--debug` is too verbose and not-`--debug` gives to little
context about where exceptions are coming from.
So, instead, it'd be nice to have `spack --backtrace` and
`SPACK_BACKTRACE=1` as methods to get something inbetween: no verbose
debug messages, but always a full backtrace.
This is useful for CI, where we don't want to drown in debug messages
when installing deps, but we do want to get details where something goes
wrong if it goes wrong.
* completion
Diffstat (limited to 'COPYRIGHT')
0 files changed, 0 insertions, 0 deletions