-
Notifications
You must be signed in to change notification settings - Fork 49
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
[chore] add CI step to build kernel with no-default-features #601
[chore] add CI step to build kernel with no-default-features #601
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #601 +/- ##
=======================================
Coverage 83.45% 83.45%
=======================================
Files 74 74
Lines 16877 16877
Branches 16877 16877
=======================================
+ Hits 14084 14085 +1
+ Misses 2135 2133 -2
- Partials 658 659 +1 ☔ View full report in Codecov by Sentry. |
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! let's just make a follow-up for testing all combinations of features
you got it! #603 |
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.
Just had the question on job vs step.
Our builds are actually broken due to a dependency on `mod engine` in `scan/mod.rs` (which only exists when one of the engine feature-flags is enabled. as soon as all are off, it fails to build). This fixes the issue by moving the `parquet_stats_skipping` module out of engine code and into `expressions` module. This was trivial since it actually doesn't depend on any engine code. We pull `parquet_stats_skipping` into `scan/mod.rs` in order to `impl ParquetStatsProvider for NoStats`. Now instead of having this rely on engine code, it's moved to the `predicates` module (which is always included) Note that I have a new test in CI that will catch this failure in the future: #601
title. Introducing since this would have caught the 0.6.0 release blocker. (
engine
code used inparquet_stats_skipping
module)