-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Migrate Optimizer tests to insta, part5 #15945
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate Optimizer tests to insta, part5 #15945
Conversation
…rs` to use snapshot assertions
…rs` to use snapshot assertions
… to use snapshot assertions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @qstommyshu -- in general
FYI @blaginin
@@ -243,48 +206,3 @@ macro_rules! assert_optimized_plan_eq_display_indent_snapshot { | |||
Ok::<(), datafusion_common::DataFusionError>(()) | |||
}}; | |||
} | |||
|
|||
pub fn assert_multi_rules_optimized_plan_eq_display_indent( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like these are dead functions, but since they were marked pub
the Rust compiler doesn't complain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥹
I wonder if we are actually done now (❤️ thanks again @qstommyshu ) |
Not yet 😅. I just checked, there are at least 5 files in optimizer tests still needs to be migrated. |
So close! |
Which issue does this PR close?
insta
#15396 , Migrate Optimizer tests to insta, part1 #15446, Migrate Optimizer tests to insta, part2 #15884, Migrate Optimizer tests to insta, part3 #15893, Migrate Optimizer tests to insta, part4 #15937Rationale for this change
What changes are included in this PR?
This is the part 5 of #15396
Are these changes tested?
Yes, I manually tested the before/after changes.
Are there any user-facing changes?
No