Deleted MPI barriers in computeQdot #609
Triggered via pull request
December 18, 2024 12:57
Status
Failure
Total duration
4h 40m 13s
Artifacts
–
Annotations
27 errors and 2 warnings
build (gfortran, RELEASE, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, RELEASE, PARALLEL, NO)
Process completed with exit code 255.
|
build (ifort, RELEASE, PARALLEL, NO)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
build (ifort, RELEASE, PARALLEL, NO)
Process completed with exit code 255.
|
build (ifort, RELEASE, PARALLEL, NO)
The operation was canceled.
|
build (ifort, RELEASE, PARALLEL, NO)
Process completed with exit code 99.
|
build (gfortran, DEBUG, PARALLEL, NO)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
build (gfortran, DEBUG, PARALLEL, NO)
The hosted runner: GitHub Actions 23 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
build (gfortran, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (ifort, DEBUG, PARALLEL, NO)
The hosted runner: GitHub Actions 30 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
build (ifort, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (ifort, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (ifort, DEBUG, PARALLEL, NO)
Process completed with exit code 99.
|
build (ifort, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (ifort, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (ifort, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (ifort, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (ifort, DEBUG, PARALLEL, NO)
Process completed with exit code 255.
|
build (gfortran, RELEASE, PARALLEL, NO)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build (ifort, DEBUG, PARALLEL, NO)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|