The self-hosted runner: buildjet.com_f6ceeddc-c13f-46b5-b252-8307aecf2127 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.

The self-hosted runner: buildjet.com_b6136b9b-15a7-4bd8-a6dc-a330d896900b 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.

The self-hosted runner: buildjet.com_b2b90f0a-48aa-4004-b643-c979906d935f 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.

The self-hosted runner: buildjet.com_ac6ac4ff-4c5a-4cb2-a895-5d99f4423d89 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.

[stdout] time="2024-08-27T10:46:45Z" level=fatal msg="Load registry failed failed to load image nginx: unable to copy from nginx to 192.168.100.229:5050/library/nginx:latest: GET https://index.docker.io/v2/library/nginx/manifests/sha256:09279664808b1f74e3698a901d94d9640f11af5986b85c3b7ca7944a7dded1be: TOOMANYREQUESTS: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit" [exit status 1] FAIL: ../registry/testdata/registry_test.txt:12: command failure

Process completed with exit code 1.

[stdout] Docker app deployment Test === RUN TestDockerStart docker_test.go:189: time: 2024-08-27T10:36:16.565993474Z out: Add app to list config changed, to see config run 'eden controller edge-node get-config' docker_test.go:195: time: 2024-08-27T10:36:17.572512457Z out: Add processing of app messages docker_test.go:199: time: 2024-08-27T10:36:17.572538967Z out: Add processing of app running messages docker_test.go:203: time: 2024-08-27T10:36:17.572546412Z out: Add function to obtain EVE IP docker_test.go:207: time: 2024-08-27T10:36:17.572552713Z out: Add trying to access app via http testProc.go:84: time: 2024-08-27T10:36:25.385181322Z out: projects.ProcTimerFunc done with return: external ip is: 127.0.0.1 testProc.go:84: time: 2024-08-27T10:37:06.134387318Z out: projects.ProcInfoFunc done with return: app found with name t1 testContext.go:302: WaitForProc terminated by timeout 20m0s testContext.go:285: WaitForProcWithErrorCallback terminated by timeout 20m0s --- FAIL: TestDockerStart (1202.19s) FAIL [stderr] time="2024-08-27T10:36:16Z" level=error msg="cannot obtain info about volumes: error getting config library/nginx:latest: reading image \"index.docker.io/library/nginx:latest\": GET https://index.docker.io/v2/library/nginx/manifests/latest: TOOMANYREQUESTS: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit" time="2024-08-27T10:36:16Z" level=error msg="cannot obtain info about disks: GET https://index.docker.io/v2/library/nginx/manifests/latest: TOOMANYREQUESTS: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit" time="2024-08-27T10:36:25Z" level=info msg="time: 2024-08-27T10:36:25.385181322Z out: projects.ProcTimerFunc done with return: external ip is: 127.0.0.1" time="2024-08-27T10:37:06Z" level=info msg="time: 2024-08-27T10:37:06.134387318Z out: projects.ProcInfoFunc done with return: app found with name t1" [exit status 1] FAIL: ../docker/testdata/2dockers_test.txt:13: command failure

Process completed with exit code 1.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/