Skip to content

Conversation

@oharboe
Copy link
Collaborator

@oharboe oharboe commented Oct 27, 2025

@jhkim-pii Warning checking at home. We have this sort of warning checking code in ORFS, but this is good 'nuf for our current purposes.

@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@maliberty
Copy link
Member

The change is fine but as the tests fail it can't be merged (and needs a tcl format)

@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2025

clang-tidy review says "All clean, LGTM! 👍"

@oharboe
Copy link
Collaborator Author

oharboe commented Nov 3, 2025

Tested warning mechanism locally by injecting false positives.

@jhkim-pii Fixed the other unexpected warnings.

@oharboe
Copy link
Collaborator Author

oharboe commented Nov 3, 2025

@maliberty automerge?

@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2025

clang-tidy review says "All clean, LGTM! 👍"

@oharboe oharboe force-pushed the power-read-spef-warning-check branch from 162eb61 to 6a50382 Compare November 3, 2025 07:20
@oharboe
Copy link
Collaborator Author

oharboe commented Nov 3, 2025

force pushed to clean up my git gaffe

@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2025

clang-tidy review says "All clean, LGTM! 👍"

@oharboe
Copy link
Collaborator Author

oharboe commented Nov 3, 2025

@vvbandeira unrelated CI error in pr-merge

image

@maliberty maliberty merged commit a5116f9 into The-OpenROAD-Project:master Nov 3, 2025
12 of 13 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