Reverted: reject infeasible greedy final routes - #156
Draft
ShiboSoftwareDev wants to merge 2 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Benchmark This PRRun benchmarks by commenting on this PR: Everything after Examples:
Any PR whose title contains |
ShiboSoftwareDev
force-pushed
the
agent/preserve-hard-constraints-in-greedy-final-route
branch
from
August 7, 2026 20:11
3700dea to
ab41ea8
Compare
This reverts commit ab41ea8.
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
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.
Status: reverted
This fix has been fully reverted because preserving the hard crossing rejection in the final greedy route caused downstream autorouter benchmark samples to fail instead of producing routed output.
The current head has the exact same Git tree as reproduction base PR #155. The reproduction remains useful evidence, but this rejection behavior should not be merged without a recovery strategy that finds a valid alternative topology or assignment.