AlexandreSinger

Note that the VPR documentation does not specify which file extensions to use for router lookahead: https://docs.verilogtorouting.org/en/latest/vpr/command_line_usage/#cmdoption-vpr-read_router_lookahead However, the documentation for the RR graph is detailed as .xml for XML...

@vaughnbetz I also saw this PR and was curious why I could not rerun the CI. I believe the reason is because the CI clears runs after a certain period...

@vaughnbetz Yeah there is something in this PR that is causing the strong tests to time out. My guess is the use of `os.getcwd()`. These scripts are often run all...

The branch conflict you are seeing regarding libcatch2 is caused by the submodule being updated in Master, but this PR is using the old version of libcatch2. This *shouldn't* cause...

I have merged the most recent version of master in and pushed the code. Git was having a bad time understanding how we upgraded the submodule, but I have verified...

@kimiatkh I am currently working on removing all of the warnings in the VTR builds (see issue #2518 ). What is the progress on this issue?

@vaughnbetz I think this issue can be closed since it was resolved in Navid's most recent PR. PR #2549

@alirezazd I am collecting all of the warnings in VTR (see issue #2518 ). Has there been any progress on resolving these issues?

@amirarjmand93 The warnings we are seeing can be found in the CI here (this is from the most recent CI build of master): https://github.com/verilog-to-routing/vtr-verilog-to-routing/actions/runs/8714477843/job/23904790647#step:6:1738 (The 2 shift reduce conflicts) It...

After this PR has been merged: pr #2543 Is this issue fully resolved?