fix: Fix local datafusion-cli test failure#21761
Merged
Dandandan merged 2 commits intoapache:mainfrom Apr 21, 2026
Merged
Conversation
Jefffrey
approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
One test case in
datafusion-clicrate is failing locally if you run all tests throughcargo nextest run, but passes forcargo testThe reason is
nextesttriggers a different build graph, which enforces a feature flag inserde_jsondependency.This PR enforces this feature in the
dev-dependenciesindatafusion-clicrate, so the test become deterministic under different test setup.#21502 Fixed a similar issue, and also explains why not enabling it in the global dependencies inside
Cargo.tomlWhat changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?