Skip to content
Spack CPU Builds

Add initial S3 Deployment with Docker container in ECR #132

Sign in to view logs

Add initial S3 Deployment with Docker container in ECR

Add initial S3 Deployment with Docker container in ECR #132

Triggered via pull request November 9, 2023 23:39
@JayapreethiJayapreethi
synchronize #4
cloud-dev
Status Failure
Total duration 17m 22s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

spack_cpu_build.yaml

on: pull_request
Matrix: Build ExaGO with Spack
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Build ExaGO with Spack (exago@develop+mpi~ipopt+hiop~python~raja ^openmpi)
Process completed with exit code 1.
Build ExaGO with Spack (exago@develop+mpi~ipopt+hiop+python~raja ^openmpi)
The operation was canceled.
Build ExaGO with Spack (exago@develop+mpi~ipopt+hiop~python+raja ^openmpi ^hiop+raja~sparse)
The operation was canceled.
Build ExaGO with Spack (exago@develop+mpi~ipopt+hiop~python~raja ^openmpi)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build ExaGO with Spack (exago@develop+mpi~ipopt+hiop+python~raja ^openmpi)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build ExaGO with Spack (exago@develop+mpi~ipopt+hiop~python+raja ^openmpi ^hiop+raja~sparse)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/