-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Do not run avro sqllogictests tests unless the avro feature is enabled #6429
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
Conversation
|
@xudong963 or @melgenek I wonder if you have time to review this PR? |
| info!("Running with DataFusion runner: {}", path.display()); | ||
| let test_ctx = context_for_test_file(&relative_path).await; | ||
| let Some(test_ctx) = context_for_test_file(&relative_path).await else { | ||
| info!("Skipping: {}", path.display()); |
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 think this will log twice, once in context_for_test_file and once here. I feel at least one of these is redundant...
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.
Yes, it will log twice. I was thinking that I wanted to log the reason the test was skipped (in context_for_test_file ) as well as make double sure that the logs showed any test that was skipped (if/when we add more tests that are skipped)
Given that the logs aren't printed by default (you need to do RUST_LOG=... to do so ) I chose the "mo logs mo better" approach, but I can see how others might have a different preference
I don't feel strongly and will change it if others prefer less logging
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.
Don't feel strongly, was just an observation
melgenek
left a comment
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.
👍
xudong963
left a comment
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.
LGTM
|
Thanks for the quick turnaround everyone!@ |
Which issue does this PR close?
Closes #6399
Rationale for this change
If a feature is not enabled, we should not fail tests . This test was newly added in #6362 by @e1ijah1 👋 ❤️ but has the unfortunate property that running
cargo test -p datafusionnow fails becauseavro.sltwill only pass if theavrofeature is enabledWhat changes are included in this PR?
Change sqllogictest so that it does not run avro.sql if the
avrofeature is not availableAre these changes tested?
Yes
Are there any user-facing changes?
You can now do:
RUST_LOG=debug cargo test -p datafusion --test sqllogictests -- avroAnd it will pass