diff options
author | Peter Scheibel <scheibel1@llnl.gov> | 2020-07-07 11:37:36 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-07-07 11:37:36 -0700 |
commit | 650ab563f42d68ea7e9bf0fe296e2b9b1e78755c (patch) | |
tree | 6dde44ad275604f07955d4ec15fca0e1d1487c3d /bin/spack-python | |
parent | 90285c7d6105d6ec1d77d207338ba4eea54cc212 (diff) | |
download | spack-650ab563f42d68ea7e9bf0fe296e2b9b1e78755c.tar.gz spack-650ab563f42d68ea7e9bf0fe296e2b9b1e78755c.tar.bz2 spack-650ab563f42d68ea7e9bf0fe296e2b9b1e78755c.tar.xz spack-650ab563f42d68ea7e9bf0fe296e2b9b1e78755c.zip |
Uninstall: tolerate hook failures when force=true (#16513)
Fixes #16478
This allows an uninstall to proceed even when encountering pre-uninstall
hook failures if the user chooses the --force option for the uninstall.
This also prevents post-uninstall hook failures from raising an exception,
which would terminate a sequence of uninstalls. This isn't likely essential
for #16478, but I think overall it will improve the user experience: if
the post-uninstall hook fails, there isn't much point in terminating a
sequence of spec uninstalls because at the point where the post-uninstall
hook is run, the spec has already been removed from the database (so it
will never have another chance to run).
Notes:
* When doing spack uninstall -a, certain pre/post-uninstall hooks aren't
important to run, but this isn't easy to track with the current model.
For example: if you are uninstalling a package and its extension, you
do not have to do the activation check for the extension.
* This doesn't handle the uninstallation of specs that are not in the DB,
so it may leave "dangling" specs in the installation prefix
Diffstat (limited to 'bin/spack-python')
0 files changed, 0 insertions, 0 deletions