pavilion2 icon indicating copy to clipboard operation
pavilion2 copied to clipboard

Spack builds fail generally, and not cleanly.

Open Paul-Ferrell opened this issue 1 year ago • 0 comments

When trying to use the Spack installer for Pavilion in a test, the build fails, and the build directory (e.g. /usr/global/tools/pavilion2/working_dir/builds/35c3479bdd814eab) no longer exists after the build failure.

Nicholas Sly 12:04 PM The test run build directory still exists (/usr/global/tools/pavilion2/working_dir/test_runs/4625/build), but the Spack environment refers to the working_dir/builds/35c... directory as where the environment is being built, despite the spack.yaml file itself being in the test_runs/####/build directory.

The spack.yaml file also refers to the working_dir/builds/35c... directory as the install_tree path. If it's not a permanent path, perhaps the working_dir/test_runs/####/build path would be better there

Paul-Ferrell avatar Jan 18 '24 20:01 Paul-Ferrell