Merge pull request #2639 from nedsels/improve_map_lookahead #9035
vaughnbetztest.yml
on: push
Matrix: B: Building VtR
Matrix: Compatibility
Matrix: Format
Matrix: Regression
Matrix: Sanitized
U: C++ Unit Tests
24m 40s
W: Check Compilation Warnings
17m 55s
Parmys Basic Test
38m 26s
ODIN-II Basic Test
49m 31s
VQM2BLIF Basic Tests
19m 49s
Matrix: Run-tests
Coverity Scan
25m 18s
Annotations
17 errors
|
Run-tests (vtr_reg_nightly_test2, 16)
The self-hosted runner: gh-actions-runner-vtr_50 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_39 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_7 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_38 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_30 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_66 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_102 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_110 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_87 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_92 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_125 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_172 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_180 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_215 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_174 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_241 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_252 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
|
714 KB |
|
|
Basic with NO_GRAPHICS_results
Expired
|
112 KB |
|
|
Basic with NO_GRAPHICS_run_files
Expired
|
714 KB |
|
|
Basic with NO_SERVER_results
Expired
|
111 KB |
|
|
Basic with NO_SERVER_run_files
Expired
|
714 KB |
|
|
Basic with VTR_ENABLE_DEBUG_LOGGING_results
Expired
|
114 KB |
|
|
Basic with VTR_ENABLE_DEBUG_LOGGING_run_files
Expired
|
723 KB |
|
|
Basic_odin with VTR_ENABLE_DEBUG_LOGGING_results
Expired
|
116 KB |
|
|
Basic_odin with VTR_ENABLE_DEBUG_LOGGING_run_files
Expired
|
656 KB |
|
|
Basic_odin_results
Expired
|
113 KB |
|
|
Basic_odin_run_files
Expired
|
645 KB |
|
|
Basic_results
Expired
|
112 KB |
|
|
Basic_run_files
Expired
|
714 KB |
|
|
Strong_odin_results
Expired
|
2.05 MB |
|
|
Strong_odin_run_files
Expired
|
11.3 MB |
|
|
Strong_results
Expired
|
2.18 MB |
|
|
Strong_run_files
Expired
|
13.4 MB |
|
|
Valgrind Memory_results
Expired
|
43.8 KB |
|
|
Valgrind Memory_run_files
Expired
|
228 KB |
|