Merge pull request #2425 from vkrm1612/issue_2342 #262
pcarruscagregression-arm64.yml
on: push
Matrix: Run the jobs on Linux ARM64 / Build SU2
Matrix: Run the jobs on Linux ARM64 / Build SU2 (asan)
Matrix: Run the jobs on Linux ARM64 / Build SU2 (tsan)
Matrix: Run the jobs on Linux ARM64 / Regression Tests
Matrix: Run the jobs on Linux ARM64 / Unit Tests
Matrix: Run the jobs on Linux ARM64 / Address Sanitizer Tests
Matrix: Run the jobs on Linux ARM64 / Thread Sanitizer Tests
Annotations
12 errors
|
Run the jobs on Linux ARM64 / Build SU2 (asan) (BaseNoMPI-asan)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Run the jobs on Linux ARM64 / Build SU2 (asan) (BaseNoMPI-asan)
Process completed with exit code 137.
|
|
Run the jobs on Linux ARM64 / Build SU2 (asan) (ReverseNoMPI-asan)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Run the jobs on Linux ARM64 / Build SU2 (asan) (ReverseNoMPI-asan)
Process completed with exit code 137.
|
|
Run the jobs on Linux ARM64 / Build SU2 (BaseMPI)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Run the jobs on Linux ARM64 / Build SU2 (ForwardMPI)
The self-hosted runner: runner-3 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Run the jobs on Linux ARM64 / Build SU2 (BaseOMP)
The self-hosted runner: runner-2 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Run the jobs on Linux ARM64 / Build SU2 (ForwardNoMPI)
The self-hosted runner: runner-8 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Run the jobs on Linux ARM64 / Build SU2 (ForwardOMP)
The self-hosted runner: runner-11 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Run the jobs on Linux ARM64 / Build SU2 (ReverseMPI)
The self-hosted runner: runner-10 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Run the jobs on Linux ARM64 / Build SU2 (ReverseNoMPI)
The self-hosted runner: runner-10 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Run the jobs on Linux ARM64 / Build SU2 (ReverseOMP)
The self-hosted runner: runner-11 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|