NightlyTest #716
vaughnbetzAnnotations
16 errors
|
Run-tests (vtr_reg_nightly_test1, 16)
The self-hosted runner: gh-actions-runner-vtr_86 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-tests (odin_reg_strong, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_134 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-tests (parmys_reg_strong, 16, -DYOSYS_F4PGA_PLUGINS=OFF)
The self-hosted runner: gh-actions-runner-vtr_239 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-tests (vtr_reg_nightly_test2_odin, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_12 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-tests (vtr_reg_nightly_test1_odin, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_132 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-tests (vtr_reg_nightly_test2, 16)
The self-hosted runner: gh-actions-runner-vtr_227 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-tests (vtr_reg_nightly_test3, 16)
The self-hosted runner: gh-actions-runner-vtr_119 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-tests (vtr_reg_nightly_test3_odin, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_15 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-tests (vtr_reg_nightly_test5, 16)
The self-hosted runner: gh-actions-runner-vtr_22 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-tests (vtr_reg_nightly_test4, 16)
The self-hosted runner: gh-actions-runner-vtr_137 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-tests (vtr_reg_nightly_test4_odin, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_70 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-tests (vtr_reg_nightly_test6, 16)
The self-hosted runner: gh-actions-runner-vtr_242 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-tests (vtr_reg_strong, 16, -DVTR_ASSERT_LEVEL=3, libeigen3-dev)
The self-hosted runner: gh-actions-runner-vtr_123 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-tests (vtr_reg_strong_odin, 16, -skip_qor, -DVTR_ASSERT_LEVEL=3 -DVTR_ENABLE_SANITIZE=ON -DWI...
The self-hosted runner: gh-actions-runner-vtr_18 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-tests (vtr_reg_nightly_test7, 16)
The self-hosted runner: gh-actions-runner-vtr_121 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-tests (vtr_reg_strong_odin, 16, -DVTR_ASSERT_LEVEL=3 -DWITH_ODIN=ON, libeigen3-dev)
The self-hosted runner: gh-actions-runner-vtr_177 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.
|