fix: gate debug-only assertions in physical planner test test_optimization_invariant_checker#23323
Merged
xudong963 merged 2 commits intoJul 5, 2026
Conversation
xudong963
approved these changes
Jul 5, 2026
xudong963
left a comment
Member
There was a problem hiding this comment.
How about using cfg!(debug_assertions) which adds an explicit assert!(result.is_ok()) for release mode and removes the need to gate InvariantFailsExtensionNode, giving strictly better coverage with less #[cfg] surface.
Contributor
Author
Thanks, I did not think of this. I've applied it just now |
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.
Which issue does this PR close?
Rationale for this change
test_optimization_invariant_checkerpanics underrelease-nonltoprofile which has debug_assertions=false. Thus, we need to gateWhat changes are included in this PR?
Make sure debug_assertion required places are behind that gate
Are these changes tested?
Yes and this is test only change.
now passes since we skip these checks as they are not supported in that profile
Are there any user-facing changes?
No