-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Improve feature flag CI coverage datafusion
and datafusion-functions
#15203
base: main
Are you sure you want to change the base?
Conversation
@@ -82,6 +82,8 @@ jobs: | |||
uses: ./.github/actions/setup-builder | |||
with: | |||
rust-version: stable | |||
- name: Check datafusion-common (default features) |
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.
there was no check for default set of features (even the tests run with avro, etc) so I added that
datafusion
and datafusion-functions
datafusion
and datafusion-functions
, remove core_expressions
feature
datafusion
and datafusion-functions
, remove core_expressions
featuredatafusion
and datafusion-functions
- name: Check datafusion-substrait (no-default-features) | ||
run: cargo check --profile ci --all-targets --no-default-features -p datafusion-substrait | ||
# | ||
# Note: Only check libraries (not --all-targets) to cover end user APIs |
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.
The idea is to test only --all-targets
for the default features (what a developer would likely run), otherwise the CI will just verify that a user of the crate can compile things rather than check all tests and benches too
@xudong963 I wonder if you have some time to review this PR? |
Which issue does this PR close?
datafusion-substrait
anddatafusion-proto
CI feature checks, increase coverage #15156Rationale for this change
I reviewed the CI coverage for datafusion's (many!) feature flag and it is haphazard -- for example it was not clear where to add a test for #15124
What changes are included in this PR?
datafusion
anddatafusion-functions
crateAre these changes tested?
Are there any user-facing changes?