This PR introduces changes to the LLNL CI pipeline.
The largest change is that the results are now uploaded to central testing dashboard sdk.testing.exaworks.org/. These results contain information about the test that was run along with the results of the test. With the current review and release system, we are not able to upload the output of the tests, just weather it passed or failed. The gitlab pipeline will print the output to the gitlab job logs in the event of a failure in case we need to manually go back and debug.
Another Change introduced in this PR is how the spack environment is built. Now, every time the pipeline is run, Spack is updated via a git pull form the spack repo, then the exaworks meta package is reinstalled with the --fresh flag. This flag ensures that if any dependencies have been updated, the newest version will be installed.
The container tests have been removed for now since podman usage has been disabled on the machine we were running on. We can consider reintroducing it when that functionality returns.
Update 6-6-2022 :
The original Spack Build at LLNL broke due to some incompatibilities with the default compiler, so I added changes that fixed the Spack Build to this PR. These changes include :
using spack environments to build on different micro architecture.
using spack to build and then use compilers compatible with the full SDK dependency chain.
adding Spack Builds for cascade lake and ppc64le to test on llnl machines ruby and Lassen respectively
This PR introduces changes to the LLNL CI pipeline.
The largest change is that the results are now uploaded to central testing dashboard sdk.testing.exaworks.org/. These results contain information about the test that was run along with the results of the test. With the current review and release system, we are not able to upload the output of the tests, just weather it passed or failed. The gitlab pipeline will print the output to the gitlab job logs in the event of a failure in case we need to manually go back and debug.
Another Change introduced in this PR is how the spack environment is built. Now, every time the pipeline is run, Spack is updated via a git pull form the spack repo, then the exaworks meta package is reinstalled with the --fresh flag. This flag ensures that if any dependencies have been updated, the newest version will be installed.
The container tests have been removed for now since podman usage has been disabled on the machine we were running on. We can consider reintroducing it when that functionality returns.
Update 6-6-2022 : The original Spack Build at LLNL broke due to some incompatibilities with the default compiler, so I added changes that fixed the Spack Build to this PR. These changes include :