diff options
author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2021-06-18 15:52:08 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-06-18 07:52:08 -0600 |
commit | 32f1aa607c9536709442c44547b31ff316e3730b (patch) | |
tree | 3dadebf576a3a23e878a4b3b2486a94bba9aead8 /NOTICE | |
parent | 8ad05d6a74ba8c1e718b51b7b3b1cd43d484d7e6 (diff) | |
download | spack-32f1aa607c9536709442c44547b31ff316e3730b.tar.gz spack-32f1aa607c9536709442c44547b31ff316e3730b.tar.bz2 spack-32f1aa607c9536709442c44547b31ff316e3730b.tar.xz spack-32f1aa607c9536709442c44547b31ff316e3730b.zip |
Add an audit system to Spack (#23053)
Add a new "spack audit" command. This command can check for issues
with configuration or with packages and is intended to help a
user debug a failed Spack build.
In some cases the reported issues are always errors but are too
costly to check for (e.g. packages that specify missing variants on
dependencies). In other cases the issues may be legitimate but
uncommon usage of Spack and we want to be sure the user intended the
behavior (e.g. duplicate compiler definitions).
Audits are grouped by theme, and for now the two themes are packages
and configuration. For example you can run all available audits
on packages with "spack audit packages". It is intended that in
the future users will be able to define their own audits.
The package audits are good candidates for running in package_sanity
(i.e. they could catch bugs in user-submitted packages before they
are merged) but that is left for a later PR.
Diffstat (limited to 'NOTICE')
0 files changed, 0 insertions, 0 deletions