You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@datafusion.apache.org by "2010YOUY01 (via GitHub)" <gi...@apache.org> on 2026/08/04 09:31:41 UTC
[PR] PoC(CI): Introduce `xtask` to keep local test and CI run in sync [datafusion]
2010YOUY01 opened a new pull request, #24083:
URL: https://github.com/apache/datafusion/pull/24083
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes #123` indicates that this PR will close issue #123.
-->
Part of https://github.com/apache/datafusion/issues/21048
## Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes.
-->
The end goal is easy local CI reproducer like
```
# run full ci tests
cargo xtask ci full
# run fast tests
cargo xtask ci fast
```
This PR only try to encapsulate single CI step with `xtask`, and hope later build towards that goal. Running test commands locally mirroring CI become easier after this PR.
For example, the default test run command is:
https://github.com/apache/datafusion/blob/26fbf4d015d7071115c5fdadf1156291d8a2afb1/.github/workflows/rust.yml#L324-L335
Now both ci and local run can be executed with
```
# Use `cargo xtask help` for the full usage
# syntax: cargo xtask ci step [step-name] [extra-args]
cargo xtask ci step test workspace
(...run tests)
# Use 'explain' to show the underlying command
cargo xtask ci step explain test workspace
(...print the full command)
```
The command is a bit verbose, since it's a common pattern (see top comments at `xtask/src/main.rs`) for all internal dev tools, so we might need additional domains like `cargo xtask benchmark [bench-name]`
### `xtask` implementation mechanism
See `xtask/src/main.rs` top comments for details.
TLDR: internal binary, no external dependencies.
### `xtask` v.s. shell script
The existing CI jobs consist of lot of similar commands, that is parameterized with features, settings, so it would be easier to implement the runner that can handle args, to make the maintenance easier.
We also want some extra functionalities, like the above `explain` feature, or more complex orchestration needed for the 'one-click local CI run' end goal.
At this complexity, I find implementing it in rust is easier than shell scripts.
## What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR.
-->
In rust CI workflow (`rust.yml`), encapsulate `cargo test ...` and `cargo check ...` family into `xtask` runner
## Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are they covered by existing tests)?
-->
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api change` label.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org
Re: [PR] feat(CI): Introduce `xtask` to keep local test and CI commands in sync [datafusion]
Posted by "2010YOUY01 (via GitHub)" <gi...@apache.org>.
2010YOUY01 closed pull request #24083: feat(CI): Introduce `xtask` to keep local test and CI commands in sync
URL: https://github.com/apache/datafusion/pull/24083
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org
Re: [PR] PoC(CI): Introduce `xtask` to keep local test and CI commands in sync [datafusion]
Posted by "kosiew (via GitHub)" <gi...@apache.org>.
kosiew commented on code in PR #24083:
URL: https://github.com/apache/datafusion/pull/24083#discussion_r3782730666
##########
xtask/src/ci_steps.rs:
##########
@@ -0,0 +1,728 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements. See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership. The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied. See the License for the
+// specific language governing permissions and limitations
+// under the License.
+
+//! CI steps that can be inspected or run through `cargo xtask`.
+
+use crate::Result;
+use std::env;
+use std::ffi::OsStr;
+use std::path::{Path, PathBuf};
+use std::process::{Command, Stdio};
+
+type StepResult<T> = std::result::Result<T, StepError>;
+type StepRunner = fn(&StepContext, &[String]) -> StepResult<CiCommand>;
+
+const CI_COMMAND: &str = "cargo xtask ci step";
+const CI_SHORTCUT: &str = "cargo ci-step";
+
+/// Metadata and implementation for one CI step.
+///
+/// Adding an entry to `CI_STEPS` makes the step dispatchable and includes its
+/// usage and description in the generated help text.
+struct StepInfo {
+ command: &'static str,
+ help_usage: &'static str,
+ help_examples: &'static [&'static str],
+ help_description: &'static str,
+ error_message: &'static str,
+ runner: StepRunner,
+}
+
+static CI_STEPS: &[StepInfo] = &[
+ StepInfo {
+ command: "check",
+ help_usage: "check <workspace|package> [default|no-default|feature]",
+ help_examples: &["check workspace", "check datafusion default"],
+ help_description: "Check workspace or package compilation",
+ error_message: "Cargo check step failed",
+ runner: StepContext::run_check,
+ },
+ StepInfo {
+ command: "test",
+ help_usage: "test <workspace|cli|doctest|ffi|benchmark-plan|benchmark-sqllogic|postgres|substrait>",
+ help_examples: &["test cli", "test workspace"],
+ help_description: "Run a CI test suite",
+ error_message: "Cargo test step failed",
+ runner: StepContext::run_test,
+ },
+];
+
+pub(crate) fn help() -> String {
+ let mut help = format!(
+ "DataFusion CI commands\n\nUsage:\n {CI_COMMAND} <step-name> [args]\n\nExamples:\n",
+ );
+ for step in CI_STEPS {
+ if let Some(example) = step.help_examples.first() {
+ help.push_str(&format!(" {CI_COMMAND} {example}\n"));
+ }
+ }
+ help.push_str(&format!(" {CI_COMMAND} explain test workspace\n"));
+
+ let command_width = CI_STEPS
+ .iter()
+ .map(|step| step.command.len())
+ .max()
+ .unwrap_or_default();
+ help.push_str("\nAvailable steps:\n");
+ for step in CI_STEPS {
+ help.push_str(&format!(
+ " {:command_width$} {}\n",
+ step.command, step.help_description
+ ));
+ }
+
+ help.push_str(&format!(
+ "\nShortcut:\n # `{CI_SHORTCUT}` is short for `{CI_COMMAND}`.\n {CI_SHORTCUT} check workspace\n\nFor more details:\n {CI_COMMAND} check --help\n"
+ ));
+ help
+}
+
+fn step_help(step: &StepInfo) -> String {
+ let mut help = format!(
+ "DataFusion CI command: {}\n\n{}\n\nUsage:\n {CI_COMMAND} {}\n\nExamples:\n",
+ step.command, step.help_description, step.help_usage,
+ );
+ for example in step.help_examples {
+ help.push_str(&format!(" {CI_COMMAND} {example}\n"));
+ }
+ if let Some(example) = step.help_examples.first() {
+ help.push_str(&format!(
+ "\nUse 'explain' to show the full command:\n {CI_COMMAND} explain {example}\n"
+ ));
+ }
+ help
+}
+
+fn find_step(command: &str) -> Result<&'static StepInfo> {
+ CI_STEPS
+ .iter()
+ .find(|step| step.command == command)
+ .ok_or_else(|| format!("unknown CI step `{command}`"))
+}
+
+pub(crate) fn is_help_arg(arg: &str) -> bool {
+ matches!(arg, "help" | "-h" | "--help")
+}
+
+pub(crate) fn run(root: &Path, args: &[String]) -> Result<()> {
+ StepContext::new(root).run(args)
+}
+
+struct StepContext {
+ root: PathBuf,
+}
+
+impl StepContext {
+ fn new(root: &Path) -> Self {
+ Self {
+ root: root.to_path_buf(),
+ }
+ }
+
+ fn run(&self, args: &[String]) -> Result<()> {
+ match args {
+ [] => {
+ print!("{}", help());
+ Ok(())
+ }
+ [help_arg] if is_help_arg(help_arg) => {
+ print!("{}", help());
+ Ok(())
+ }
+ [step_name, help_arg] if is_help_arg(help_arg) => {
+ print!("{}", step_help(find_step(step_name)?));
+ Ok(())
+ }
+ step_args => {
+ let (action, step, command) = self.ci_step(step_args)?;
+ match action {
+ StepAction::Execute => command.execute(step.error_message),
+ StepAction::Explain => {
+ command.explain();
+ Ok(())
+ }
+ }
+ }
+ }
+ }
+
+ /// Parses a CI step into an action and its complete command description.
+ /// Keeping execution out of this method guarantees `explain` and execution
+ /// use exactly the same program, arguments, environment, and directory.
+ fn ci_step(
+ &self,
+ args: &[String],
+ ) -> Result<(StepAction, &'static StepInfo, CiCommand)> {
+ let (action, args) = match args.split_first() {
+ Some((arg, args)) if arg == "explain" => (StepAction::Explain, args),
+ _ => (StepAction::Execute, args),
+ };
+ let Some((step, args)) = args.split_first() else {
+ return Err(format!("missing CI step\n\n{}", help()));
+ };
+
+ let step = find_step(step)?;
+ let command = (step.runner)(self, args).map_err(|error| error.render(step))?;
+ Ok((action, step, command))
+ }
+
+ fn run_check(&self, args: &[String]) -> StepResult<CiCommand> {
+ let args = args.iter().map(String::as_str).collect::<Vec<_>>();
+ let mut command = self.cargo();
+ command.args(["check", "--profile", "ci"]);
+
+ match args.as_slice() {
+ ["workspace"] => {
+ command.args([
+ "--workspace",
+ "--all-targets",
+ "--features",
+ "integration-tests",
+ "--locked",
+ ]);
+ }
+ [package, "default"] => {
+ command.args(["--all-targets", "-p", package]);
+ }
+ [package, "no-default"] => {
+ command.args(["--no-default-features", "-p", package]);
+ }
+ [package, feature] => {
+ command.args([
+ "--no-default-features",
+ "-p",
+ package,
+ "--features",
+ feature,
+ ]);
+ }
+ _ => return Err(StepError::Usage),
+ }
+
+ Ok(command)
+ }
+
+ fn run_test(&self, args: &[String]) -> StepResult<CiCommand> {
Review Comment:
Could we add table-driven assertions for each `test` variant's argv, working directory, and explicit environment?
The existing tests cover the `check` variants well, but for `test` we currently only inspect the formatted explanation of one variant. Since these commands are intended to mirror CI exactly, direct command-shape tests would make it easier to catch accidental changes to features, profiles, environment variables, or working directories in future edits.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org
Re: [PR] PoC(CI): Introduce `xtask` to keep local test and CI commands in sync [datafusion]
Posted by "2010YOUY01 (via GitHub)" <gi...@apache.org>.
2010YOUY01 commented on code in PR #24083:
URL: https://github.com/apache/datafusion/pull/24083#discussion_r3812447188
##########
xtask/src/ci_steps.rs:
##########
@@ -0,0 +1,728 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements. See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership. The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied. See the License for the
+// specific language governing permissions and limitations
+// under the License.
+
+//! CI steps that can be inspected or run through `cargo xtask`.
+
+use crate::Result;
+use std::env;
+use std::ffi::OsStr;
+use std::path::{Path, PathBuf};
+use std::process::{Command, Stdio};
+
+type StepResult<T> = std::result::Result<T, StepError>;
+type StepRunner = fn(&StepContext, &[String]) -> StepResult<CiCommand>;
+
+const CI_COMMAND: &str = "cargo xtask ci step";
+const CI_SHORTCUT: &str = "cargo ci-step";
+
+/// Metadata and implementation for one CI step.
+///
+/// Adding an entry to `CI_STEPS` makes the step dispatchable and includes its
+/// usage and description in the generated help text.
+struct StepInfo {
+ command: &'static str,
+ help_usage: &'static str,
+ help_examples: &'static [&'static str],
+ help_description: &'static str,
+ error_message: &'static str,
+ runner: StepRunner,
+}
+
+static CI_STEPS: &[StepInfo] = &[
+ StepInfo {
+ command: "check",
+ help_usage: "check <workspace|package> [default|no-default|feature]",
+ help_examples: &["check workspace", "check datafusion default"],
+ help_description: "Check workspace or package compilation",
+ error_message: "Cargo check step failed",
+ runner: StepContext::run_check,
+ },
+ StepInfo {
+ command: "test",
+ help_usage: "test <workspace|cli|doctest|ffi|benchmark-plan|benchmark-sqllogic|postgres|substrait>",
+ help_examples: &["test cli", "test workspace"],
+ help_description: "Run a CI test suite",
+ error_message: "Cargo test step failed",
+ runner: StepContext::run_test,
+ },
+];
+
+pub(crate) fn help() -> String {
+ let mut help = format!(
+ "DataFusion CI commands\n\nUsage:\n {CI_COMMAND} <step-name> [args]\n\nExamples:\n",
+ );
+ for step in CI_STEPS {
+ if let Some(example) = step.help_examples.first() {
+ help.push_str(&format!(" {CI_COMMAND} {example}\n"));
+ }
+ }
+ help.push_str(&format!(" {CI_COMMAND} explain test workspace\n"));
+
+ let command_width = CI_STEPS
+ .iter()
+ .map(|step| step.command.len())
+ .max()
+ .unwrap_or_default();
+ help.push_str("\nAvailable steps:\n");
+ for step in CI_STEPS {
+ help.push_str(&format!(
+ " {:command_width$} {}\n",
+ step.command, step.help_description
+ ));
+ }
+
+ help.push_str(&format!(
+ "\nShortcut:\n # `{CI_SHORTCUT}` is short for `{CI_COMMAND}`.\n {CI_SHORTCUT} check workspace\n\nFor more details:\n {CI_COMMAND} check --help\n"
+ ));
+ help
+}
+
+fn step_help(step: &StepInfo) -> String {
+ let mut help = format!(
+ "DataFusion CI command: {}\n\n{}\n\nUsage:\n {CI_COMMAND} {}\n\nExamples:\n",
+ step.command, step.help_description, step.help_usage,
+ );
+ for example in step.help_examples {
+ help.push_str(&format!(" {CI_COMMAND} {example}\n"));
+ }
+ if let Some(example) = step.help_examples.first() {
+ help.push_str(&format!(
+ "\nUse 'explain' to show the full command:\n {CI_COMMAND} explain {example}\n"
+ ));
+ }
+ help
+}
+
+fn find_step(command: &str) -> Result<&'static StepInfo> {
+ CI_STEPS
+ .iter()
+ .find(|step| step.command == command)
+ .ok_or_else(|| format!("unknown CI step `{command}`"))
+}
+
+pub(crate) fn is_help_arg(arg: &str) -> bool {
+ matches!(arg, "help" | "-h" | "--help")
+}
+
+pub(crate) fn run(root: &Path, args: &[String]) -> Result<()> {
+ StepContext::new(root).run(args)
+}
+
+struct StepContext {
+ root: PathBuf,
+}
+
+impl StepContext {
+ fn new(root: &Path) -> Self {
+ Self {
+ root: root.to_path_buf(),
+ }
+ }
+
+ fn run(&self, args: &[String]) -> Result<()> {
+ match args {
+ [] => {
+ print!("{}", help());
+ Ok(())
+ }
+ [help_arg] if is_help_arg(help_arg) => {
+ print!("{}", help());
+ Ok(())
+ }
+ [step_name, help_arg] if is_help_arg(help_arg) => {
+ print!("{}", step_help(find_step(step_name)?));
+ Ok(())
+ }
+ step_args => {
+ let (action, step, command) = self.ci_step(step_args)?;
+ match action {
+ StepAction::Execute => command.execute(step.error_message),
+ StepAction::Explain => {
+ command.explain();
+ Ok(())
+ }
+ }
+ }
+ }
+ }
+
+ /// Parses a CI step into an action and its complete command description.
+ /// Keeping execution out of this method guarantees `explain` and execution
+ /// use exactly the same program, arguments, environment, and directory.
+ fn ci_step(
+ &self,
+ args: &[String],
+ ) -> Result<(StepAction, &'static StepInfo, CiCommand)> {
+ let (action, args) = match args.split_first() {
+ Some((arg, args)) if arg == "explain" => (StepAction::Explain, args),
+ _ => (StepAction::Execute, args),
+ };
+ let Some((step, args)) = args.split_first() else {
+ return Err(format!("missing CI step\n\n{}", help()));
+ };
+
+ let step = find_step(step)?;
+ let command = (step.runner)(self, args).map_err(|error| error.render(step))?;
+ Ok((action, step, command))
+ }
+
+ fn run_check(&self, args: &[String]) -> StepResult<CiCommand> {
+ let args = args.iter().map(String::as_str).collect::<Vec<_>>();
+ let mut command = self.cargo();
+ command.args(["check", "--profile", "ci"]);
+
+ match args.as_slice() {
+ ["workspace"] => {
+ command.args([
+ "--workspace",
+ "--all-targets",
+ "--features",
+ "integration-tests",
+ "--locked",
+ ]);
+ }
+ [package, "default"] => {
+ command.args(["--all-targets", "-p", package]);
+ }
+ [package, "no-default"] => {
+ command.args(["--no-default-features", "-p", package]);
+ }
+ [package, feature] => {
+ command.args([
+ "--no-default-features",
+ "-p",
+ package,
+ "--features",
+ feature,
+ ]);
+ }
+ _ => return Err(StepError::Usage),
+ }
+
+ Ok(command)
+ }
+
+ fn run_test(&self, args: &[String]) -> StepResult<CiCommand> {
Review Comment:
Thank you for the review!
Updated in [2cf7dc4](https://github.com/apache/datafusion/pull/24083/commits/2cf7dc431fa2e98150cc4144b165c45701d1b145), I try to organize the tests differently to make them simpler, and also ensure all variants are covered.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org
Re: [PR] feat(CI): Introduce `xtask` to keep local test and CI commands in sync [datafusion]
Posted by "2010YOUY01 (via GitHub)" <gi...@apache.org>.
2010YOUY01 merged PR #24083:
URL: https://github.com/apache/datafusion/pull/24083
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org
Re: [PR] PoC(CI): Introduce `xtask` to keep local test and CI commands in sync [datafusion]
Posted by "codecov-commenter (via GitHub)" <gi...@apache.org>.
codecov-commenter commented on PR #24083:
URL: https://github.com/apache/datafusion/pull/24083#issuecomment-5177944129
## [Codecov](https://app.codecov.io/gh/apache/datafusion/pull/24083?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) Report
:x: Patch coverage is `63.36996%` with `200 lines` in your changes missing coverage. Please review.
:white_check_mark: Project coverage is 80.86%. Comparing base ([`9051efd`](https://app.codecov.io/gh/apache/datafusion/commit/9051efdb87cd417b632e69759ed65e119bd06360?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)) to head ([`6a25550`](https://app.codecov.io/gh/apache/datafusion/commit/6a2555099e15e4d9986fecf66439fc54f6d83bd8?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)).
:warning: Report is 12 commits behind head on main.
| [Files with missing lines](https://app.codecov.io/gh/apache/datafusion/pull/24083?dropdown=coverage&src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Patch % | Lines |
|---|---|---|
| [xtask/src/ci\_steps.rs](https://app.codecov.io/gh/apache/datafusion/pull/24083?src=pr&el=tree&filepath=xtask%2Fsrc%2Fci_steps.rs&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-eHRhc2svc3JjL2NpX3N0ZXBzLnJz) | 67.18% | [162 Missing and 7 partials :warning: ](https://app.codecov.io/gh/apache/datafusion/pull/24083?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
| [xtask/src/main.rs](https://app.codecov.io/gh/apache/datafusion/pull/24083?src=pr&el=tree&filepath=xtask%2Fsrc%2Fmain.rs&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-eHRhc2svc3JjL21haW4ucnM=) | 0.00% | [31 Missing :warning: ](https://app.codecov.io/gh/apache/datafusion/pull/24083?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
<details><summary>Additional details and impacted files</summary>
```diff
@@ Coverage Diff @@
## main #24083 +/- ##
==========================================
- Coverage 80.87% 80.86% -0.02%
==========================================
Files 1101 1104 +3
Lines 375716 376657 +941
Branches 375716 376657 +941
==========================================
+ Hits 303874 304587 +713
- Misses 53739 53953 +214
- Partials 18103 18117 +14
```
</details>
[:umbrella: View full report in Codecov by Harness](https://app.codecov.io/gh/apache/datafusion/pull/24083?dropdown=coverage&src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
:loudspeaker: Have feedback on the report? [Share it here](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
<details><summary> :rocket: New features to boost your workflow: </summary>
- :snowflake: [Test Analytics](https://docs.codecov.com/docs/test-analytics): Detect flaky tests, report on failures, and find test suite problems.
- :package: [JS Bundle Analysis](https://docs.codecov.com/docs/javascript-bundle-analysis): Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org