summaryrefslogtreecommitdiff
path: root/var
diff options
context:
space:
mode:
authorZack Galbreath <zack.galbreath@kitware.com>2018-11-06 19:09:47 -0500
committerTodd Gamblin <tgamblin@llnl.gov>2018-11-06 16:09:47 -0800
commit30eda8b837940a884cdad850ff6c6e259d450a16 (patch)
tree830c57dfae3f8e1fe9bdbb35c7baa7bb88bc9116 /var
parenta474d83d586bd0258c0a15473b049ab95b6e48a9 (diff)
downloadspack-30eda8b837940a884cdad850ff6c6e259d450a16.tar.gz
spack-30eda8b837940a884cdad850ff6c6e259d450a16.tar.bz2
spack-30eda8b837940a884cdad850ff6c6e259d450a16.tar.xz
spack-30eda8b837940a884cdad850ff6c6e259d450a16.zip
cdash: report clean results to CDash server (#9564)
* Record stdout for packages without errors Previously our reporter only stored stdout if something went wrong while installing a package. This prevented us from properly reporting on steps where everything went as expected. * More robustly report all phases to CDash Previously if a phase generated no output it would not be reported to CDash. For example, consider the following output: ==> Executing phase: 'configure' ==> Executing phase: 'build' This would not generate a report for the configure phase. Now it does. * Add test case for CDash reporting clean builds * Fix default directory for CDash reports The default 'cdash_report' directory name was getting overwritten by 'junit-report'. * Upload the build phase first to CDash Older versions of CDash expect Build.xml to be the first file uploaded for any given build. * Define cdash_phase before referring to it
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions