-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add spack spec to log #851
Conversation
|
e8eda66
to
bd65d3b
Compare
9b2dbd5
to
8a7056b
Compare
launch jenkins all |
balfrin🟢 unit test
🟢 integration test
🔴 system test
WARNING: Serial tests did not run for system tests |
daint🟢 unit test
🟢 integration test
🔴 system test
WARNING: Serial tests did not run for system tests |
launch jenkins all |
tsa🟢 unit test
🟢 integration test
🔴 system test
WARNING: Serial tests did not run for system tests |
balfrin🟢 unit test
🟢 integration test
🔴 system test
WARNING: Serial tests did not run for system tests |
daint🟢 unit test
🟢 integration test
🔴 system test
WARNING: Serial tests did not run for system tests |
launch jenkins all |
tsa🟢 unit test
🟢 integration test
🔴 system test
WARNING: Serial tests did not run for system tests |
daint🟢 unit test
🟢 integration test
🔴 system test
WARNING: Serial tests did not run for system tests |
balfrin🟢 unit test
🟢 integration test
🔴 system test
WARNING: Serial tests did not run for system tests |
launch jenkins all |
tsa🟢 unit test
🟢 integration test
🟢 system test
|
balfrin🟢 unit test
🟢 integration test
🟢 system test
|
daint🟢 unit test
🟢 integration test
🟢 system test
|
Simplifies problem hunting, when a spec concretizes differently in a user's spack instance and Jenkins' spack instance. This normally happens when users have preinstalled packages they are unaware of.