Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spack builds fail generally, and not cleanly. #730

Open
Paul-Ferrell opened this issue Jan 18, 2024 · 0 comments
Open

Spack builds fail generally, and not cleanly. #730

Paul-Ferrell opened this issue Jan 18, 2024 · 0 comments

Comments

@Paul-Ferrell
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant