summaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
authorTodd Gamblin <tgamblin@llnl.gov>2018-07-23 01:38:09 -0700
committerTodd Gamblin <tgamblin@llnl.gov>2018-07-23 07:27:48 -0700
commit305c95b69fec32cbde60d59e9a538be49c857a83 (patch)
treed89599fb1508e047180246ff0cc826adc3926440 /lib
parent0cef7b435596f8d283143f5466fddc25adbe292d (diff)
downloadspack-305c95b69fec32cbde60d59e9a538be49c857a83.tar.gz
spack-305c95b69fec32cbde60d59e9a538be49c857a83.tar.bz2
spack-305c95b69fec32cbde60d59e9a538be49c857a83.tar.xz
spack-305c95b69fec32cbde60d59e9a538be49c857a83.zip
tests: move doc tests to the unit test stage
- Frequently, the documentation build will fail mysteriously in some spack command. - The cause is some new bug introduced by the PR, but this is not apparent because the unit tests haven't run and the doc tests aren't targeted at code bugs. - Users end up puzzled by doc failures when they're really code failures. - Move the doc tests parallel with the code tests, so that we can more easily see bugs like this.
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions