Skip to content

[RegTest] Temporarily disable strong_multiclock test for parallel connection router #3047

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

ueqri
Copy link
Contributor

@ueqri ueqri commented May 15, 2025

Temporarily disabled the strong_multiclock test in vtr_reg_strong CI regression tests for the parallel connection router, due to some random failures as mentioned in Issue #3029.

After fixing the problem with the strong_multiclock test, this will be reactivated.

…outer

Temporarily disabled the `strong_multiclock` test in `vtr_reg_strong` CI
regression tests for the parallel connection router, due to some random
failures as mentioned in Issue verilog-to-routing#3029.

After fixing the problem with the `strong_multiclock` test, this will be
reactivated.
Removed the golden results of parallel connection router test cases for
`strong_multiclock` regression test.
@vaughnbetz vaughnbetz merged commit 091314c into verilog-to-routing:master May 16, 2025
66 of 67 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants