Skip to content

[vpr][place] Placement move primitive refactoring #9040

[vpr][place] Placement move primitive refactoring

[vpr][place] Placement move primitive refactoring #9040

Triggered via pull request July 24, 2024 03:56
Status Failure
Total duration 55m 39s
Artifacts 18

test.yml

on: pull_request
Matrix: B: Building VtR
Matrix: Compatibility
Matrix: Format
Matrix: Regression
Matrix: Sanitized
U: C++ Unit Tests
24m 47s
U: C++ Unit Tests
W: Check Compilation Warnings
20m 20s
W: Check Compilation Warnings
Parmys Basic Test
38m 53s
Parmys Basic Test
ODIN-II Basic Test
47m 18s
ODIN-II Basic Test
VQM2BLIF Basic Tests
22m 31s
VQM2BLIF Basic Tests
Matrix: Run-tests
Coverity Scan
0s
Coverity Scan
Fit to window
Zoom out
Zoom in

Annotations

19 errors and 2 warnings
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 (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_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 (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 (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_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_test4_odin, 16, -DWITH_ODIN=ON)
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.
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_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_nightly_test7, 16)
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_strong, 16, -DVTR_ASSERT_LEVEL=3, libeigen3-dev)
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_strong_odin, 16, -DVTR_ASSERT_LEVEL=3 -DWITH_ODIN=ON, libeigen3-dev)
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_strong_odin, 16, -skip_qor, -DVTR_ASSERT_LEVEL=3 -DVTR_ENABLE_SANITIZE=ON -DWI...
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.
R: Basic_odin with VTR_ENABLE_DEBUG_LOGGING
Process completed with exit code 2.
R: Basic with VTR_ENABLE_DEBUG_LOGGING
Process completed with exit code 2.
R: Basic_odin with VTR_ENABLE_DEBUG_LOGGING
No files were found with the provided path: vtr_flow/**/*.log vtr_flow/**/parse_results*.txt. No artifacts will be uploaded.
R: Basic with VTR_ENABLE_DEBUG_LOGGING
No files were found with the provided path: vtr_flow/**/*.log vtr_flow/**/parse_results*.txt. No artifacts will be uploaded.

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_run_files Expired
2.76 KB
Basic_odin with VTR_ENABLE_DEBUG_LOGGING_run_files Expired
2.76 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.4 KB
Valgrind Memory_run_files Expired
228 KB