Replace ubuntu for all modules using it - meta PR #3939
Triggered via pull request
December 13, 2024 10:51
Status
Cancelled
Total duration
26m 4s
Artifacts
–
Annotations
21 errors and 2 warnings
Test | conda | 3
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Test | conda | 3
The operation was canceled.
|
Test | singularity | 2
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Test | singularity | 2
The operation was canceled.
|
Test | conda | 2
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Test | conda | 2
The operation was canceled.
|
Test | docker_self_hosted | 3
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Test | docker_self_hosted | 3
The operation was canceled.
|
Test | singularity | 1
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Test | singularity | 1
The operation was canceled.
|
Test | docker_self_hosted | 5
The self-hosted runner: ubuntu-2204-x64_i-09c42b0ae557eb5d6 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.
|
Test | docker_self_hosted | 4
The self-hosted runner: ubuntu-2204-x64_i-0c14305b3949446a6 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.
|
Test | singularity | 4
The self-hosted runner: ubuntu-2204-x64_i-0c5d02ac6d8afe8b0 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.
|
Test | docker_self_hosted | 2
Canceling since a higher priority waiting request for 'Run nf-test-7215' exists
|
Test | singularity | 3
Canceling since a higher priority waiting request for 'Run nf-test-7215' exists
|
Test | singularity | 5
Canceling since a higher priority waiting request for 'Run nf-test-7215' exists
|
Test | docker_self_hosted | 1
Canceling since a higher priority waiting request for 'Run nf-test-7215' exists
|
Test | conda | 4
Canceling since a higher priority waiting request for 'Run nf-test-7215' exists
|
Test | conda | 1
Canceling since a higher priority waiting request for 'Run nf-test-7215' exists
|
Test | conda | 5
Canceling since a higher priority waiting request for 'Run nf-test-7215' exists
|
confirm-pass
Process completed with exit code 1.
|
nf-test-changes
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
confirm-pass
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|