summaryrefslogtreecommitdiff
path: root/bin/spack-python
diff options
context:
space:
mode:
authorTamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>2021-05-11 10:37:48 -0700
committerGitHub <noreply@github.com>2021-05-11 10:37:48 -0700
commit066d33b4b36a0db087a9143fcc02ba43d1c58e15 (patch)
tree271a398d5ff871ed7825e14b0b65b645e06ca8e1 /bin/spack-python
parentdee419c1d5e3da4ef5b92edd24750d6bd8684460 (diff)
downloadspack-066d33b4b36a0db087a9143fcc02ba43d1c58e15.tar.gz
spack-066d33b4b36a0db087a9143fcc02ba43d1c58e15.tar.bz2
spack-066d33b4b36a0db087a9143fcc02ba43d1c58e15.tar.xz
spack-066d33b4b36a0db087a9143fcc02ba43d1c58e15.zip
Documentation: Refinement of "Checking an installation" (#22210)
There have been a lot of questions and some confusion recently surrounding Spack installation test capabilities so this PR is intended to clean up and refine the documentation for "Checking an installation". It aims to better distinguish between checks that are performed during an installation (i.e., build-time tests) and those that can be done days and weeks after the software has been installed (i.e., install (or smoke) tests).
Diffstat (limited to 'bin/spack-python')
0 files changed, 0 insertions, 0 deletions