[scheduling] Clean up after adding slack variables for SDC scheduling errors #3600
+236
−31
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
… errors A new test case is added to `pipeline_scheduling_pass_test` to verify behavior when rerunning scheduling after a failure due to a tight clock period. Along with a small patch to our error reporting, this should ensure we always give the best explanation we can, given what the user requested. PiperOrigin-RevId: 848165775
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
[scheduling] Clean up after adding slack variables for SDC scheduling errors
A new test case is added to
pipeline_scheduling_pass_testto verify behavior when rerunning scheduling after a failure due to a tight clock period.Along with a small patch to our error reporting, this should ensure we always give the best explanation we can, given what the user requested.