Skip to content
Snippets Groups Projects
Commit c428d04c authored by Eleni Mathioulaki's avatar Eleni Mathioulaki
Browse files

fix log collection

parent 7cb9d2c5
No related branches found
No related tags found
No related merge requests found
......@@ -187,10 +187,10 @@ build-spack-env-on-runner:
- mkdir spack_logs
# succesfully installed packages: keep the spack logs for any package modified during this CI job
- cp --parents $SPACK_DEV_PATH/opt/spack/linux-ubuntu20.04-x86_64/gcc-10.3.0/*/.spack/*.txt ./
- mv .$SPACK_DEV_PATH/opt/spack/linux-ubuntu20.04-x86_64/gcc-10.3.0 spack_logs/installed
- mv .$SPACK_DEV_PATH/opt/spack/linux-ubuntu20.04-x86_64/gcc-10.3.0 spack_logs/installed || echo "No logs for installed packages"
# not succesfully installed packages: also keep the spack logs for any packages that failed
- cp --parents /tmp/$(whoami)/spack-stage/*/*.txt ./
- mv ./tmp/$(whoami)/spack-stage spack_logs/not_installed
- mv ./tmp/$(whoami)/spack-stage spack_logs/not_installed || echo "No logs for not-installed packages"
artifacts:
paths:
- spack_logs
......@@ -251,10 +251,10 @@ sync-gitlab-spack-instance:
# succesfully installed packages: keep the spack logs for any package modified during this CI job
# (we use repo.yaml, that is modified at each start of the pipeline, as a reference file)
- find $SPACK_PATH/opt/spack/linux-ubuntu20.04-x86_64/gcc-10.3.0/*/.spack/*.txt -newer $SPACK_REPO_PATH/repo.yaml -exec cp --parents -r "{}" ./ \;
- mv .$SPACK_PATH/opt/spack/linux-ubuntu20.04-x86_64/gcc-10.3.0 spack_logs/installed
- mv .$SPACK_PATH/opt/spack/linux-ubuntu20.04-x86_64/gcc-10.3.0 spack_logs/installed || echo "No logs for installed packages"
# not succesfully installed packages: also keep the spack logs for any packages that failed
- cp --parents /tmp/$(whoami)/spack-stage/*/*.txt ./
- mv ./tmp/$(whoami)/spack-stage spack_logs/not_installed
- mv ./tmp/$(whoami)/spack-stage spack_logs/not_installed || echo "No logs for not-installed packages"
artifacts:
paths:
- spack_logs
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment