Skip to content

Adding ONT read support for ampliseq #360

Adding ONT read support for ampliseq

Adding ONT read support for ampliseq #360

Triggered via pull request July 13, 2026 11:25
Status Cancelled
Total duration 50m 7s
Artifacts

nf-test.yml

on: pull_request
nf-test-changes
16s
nf-test-changes
Matrix: nf-test
confirm-pass
6s
confirm-pass
Fit to window
Zoom out
Zoom in

Annotations

7 errors
docker | 25.10.4 | 12/17
The operation was canceled.
docker | 25.10.4 | 8/17
The self-hosted runner 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.
docker | 25.10.4 | 10/17
The self-hosted runner 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.
docker | latest-everything | 7/17
The self-hosted runner 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.
docker | latest-everything | 12/17
The self-hosted runner 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.
docker | 25.10.4 | 7/17
The self-hosted runner 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.
confirm-pass
Process completed with exit code 1.