fixing regex issue with fixed_chan_width parse file #1820
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The lint failure is fixed by Seyed in another PR that's been merged. Just relaunched the jobs. |
|
@vaughnbetz CI has gone green. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, some routing stats are not getting parsed out of vpr.out properly. This PR fixes the regex expressions in vpr.route_fixed_chan_width.txt and updates golden_results for all titan tests since they use a fixed routing channel width.
Related Issue
Motivation and Context
Bug fix :)
How Has This Been Tested?
The new golden_results have been generated locally on wintermute. Currently, golden_results for titan tests have -1 for total_connections_routed, total_heap_pushes, total_heap_pops, and total_connections_routed. This has been fixed.
Types of changes
Checklist: