Skip to content

Conversation

@AlexandreSinger
Copy link
Contributor

I expect the sanitized test to be the tall pole for the speed of the CI due to its long run time on the testcases. After investigating with Vaughn, we realized that this test was using the debug build of VTR. This was likely making it much slower than it needed to be.

To improve the speed of this test, moved it to use the release build. We still want symbols to give good error messages.

I expect the sanitized test to be the tall pole for the speed of the CI
due to its long run time on the testcases. After investigating with
Vaughn, we realized that this test was using the debug build of VTR.
This was likely making it much slower than it needed to be.

To improve the speed of this test, moved it to use the release build. We
still want symbols to give good error messages.
@github-actions github-actions bot added the infra Project Infrastructure label Jul 7, 2025
@AlexandreSinger
Copy link
Contributor Author

Prior to this change, the sanitized run took 15 minutes (with the build taking a little under a minute).

After this change, the sanitized run takes around 6 minutes (with the build expected to take around 3 minutes).

@AmirhosseinPoolad
Copy link
Contributor

Nice gains! I'm seeing an absurd amount of compiler warnings in the CI run for this PR, do you know what's the reason for those?
https://github.com/verilog-to-routing/vtr-verilog-to-routing/actions/runs/16127998530/job/45509408278?pr=3190

LGTM other than that.

@AlexandreSinger
Copy link
Contributor Author

Nice gains! I'm seeing an absurd amount of compiler warnings in the CI run for this PR, do you know what's the reason for those? https://github.com/verilog-to-routing/vtr-verilog-to-routing/actions/runs/16127998530/job/45509408278?pr=3190

LGTM other than that.

Good eye! I did not notice that. I gave it a quick look and it seems to be coming from a "maybe uninitialized" warning. I am not concerned about it; however its good to be aware of.

I believe this is similar to the IPO warnings that we suppressed which get revealed when more optimizations are performed. Since we do not care about being warning clean for this build, I do not think any action is necessary. Thanks for pointing it out!

@AlexandreSinger AlexandreSinger merged commit b26c43a into master Jul 8, 2025
30 checks passed
@AlexandreSinger AlexandreSinger deleted the feature-ci-build-cleanup branch July 8, 2025 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infra Project Infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants