Trying to fix the failing unit test #601
Triggered via pull request
October 30, 2024 16:17
soheilshahrouz
Status
Cancelled
Total duration
10m 6s
Artifacts
–
Annotations
32 errors
|
Run-tests (parmys_reg_strong, 16, -DYOSYS_F4PGA_PLUGINS=OFF)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (parmys_reg_strong, 16, -DYOSYS_F4PGA_PLUGINS=OFF)
The self-hosted runner: gh-actions-runner-vtr_158 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)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (odin_reg_strong, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_236 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, 16)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test1, 16)
The self-hosted runner: gh-actions-runner-vtr_149 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)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test2, 16)
The self-hosted runner: gh-actions-runner-vtr_246 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)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test1_odin, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_100 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)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test4, 16)
The self-hosted runner: gh-actions-runner-vtr_114 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)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test5, 16)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test2_odin, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_235 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_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_test3, 16)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test3, 16)
The self-hosted runner: gh-actions-runner-vtr_143 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)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test4_odin, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_107 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)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test3_odin, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_48 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)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test6, 16)
The self-hosted runner: gh-actions-runner-vtr_52 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...
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
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_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-tests (vtr_reg_strong_odin, 16, -DVTR_ASSERT_LEVEL=3 -DWITH_ODIN=ON, libeigen3-dev)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_nightly_test7, 16)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_strong_odin, 16, -DVTR_ASSERT_LEVEL=3 -DWITH_ODIN=ON, libeigen3-dev)
The self-hosted runner: gh-actions-runner-vtr_62 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_233 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)
Canceling since a higher priority waiting request for 'NightlyTest-2735' exists
|
|
Run-tests (vtr_reg_strong, 16, -DVTR_ASSERT_LEVEL=3, libeigen3-dev)
The self-hosted runner: gh-actions-runner-vtr_195 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.
|