Test #9029
acomoditest.yml
on: schedule
Matrix: B: Building VtR
Matrix: Compatibility
Matrix: Format
Matrix: Regression
Matrix: Sanitized
U: C++ Unit Tests
25m 11s
W: Check Compilation Warnings
25m 12s
Parmys Basic Test
39m 52s
ODIN-II Basic Test
49m 48s
VQM2BLIF Basic Tests
21m 45s
Matrix: Run-tests
Coverity Scan
29m 8s
Annotations
17 errors
|
Run-tests (odin_reg_strong, 16, -DWITH_ODIN=ON)
The self-hosted runner: gh-actions-runner-vtr_47 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=ON)
The self-hosted runner: gh-actions-runner-vtr_238 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)
The self-hosted runner: gh-actions-runner-vtr_165 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_138 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_106 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_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_73 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_245 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_167 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_80 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_49 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_40 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_214 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_system_verilog, 16, -DYOSYS_F4PGA_PLUGINS=ON)
The self-hosted runner: gh-actions-runner-vtr_151 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_44 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_84 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_82 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.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
Basic with CAPNPROTO disabled_results
Expired
|
111 KB |
|
|
Basic with CAPNPROTO disabled_run_files
Expired
|
710 KB |
|
|
Basic with NO_GRAPHICS_results
Expired
|
112 KB |
|
|
Basic with NO_GRAPHICS_run_files
Expired
|
710 KB |
|
|
Basic with NO_SERVER_results
Expired
|
112 KB |
|
|
Basic with NO_SERVER_run_files
Expired
|
710 KB |
|
|
Basic with VTR_ENABLE_DEBUG_LOGGING_results
Expired
|
114 KB |
|
|
Basic with VTR_ENABLE_DEBUG_LOGGING_run_files
Expired
|
718 KB |
|
|
Basic_odin with VTR_ENABLE_DEBUG_LOGGING_results
Expired
|
115 KB |
|
|
Basic_odin with VTR_ENABLE_DEBUG_LOGGING_run_files
Expired
|
658 KB |
|
|
Basic_odin_results
Expired
|
112 KB |
|
|
Basic_odin_run_files
Expired
|
647 KB |
|
|
Basic_results
Expired
|
112 KB |
|
|
Basic_run_files
Expired
|
710 KB |
|
|
Strong_odin_results
Expired
|
2.06 MB |
|
|
Strong_odin_run_files
Expired
|
11.3 MB |
|
|
Strong_results
Expired
|
2.17 MB |
|
|
Strong_run_files
Expired
|
13.3 MB |
|
|
Valgrind Memory_results
Expired
|
43.9 KB |
|
|
Valgrind Memory_run_files
Expired
|
228 KB |
|