[MINOR][SQL][TESTS] Optimize the run tests command in the doc of suites in docker-integration-tests module
#47218
Conversation
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
Member
|
I'm not sure if it's good or not, sometimes new changes do require scanning other modules |
Contributor
Author
|
Just referring to #44597, in this scenario, we only need to run a single suite? |
Member
|
I'm not an expert on this, but sometimes I fail to run tests due to compilation errors with the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changes were proposed in this pull request?
This PR aims to optimize the run tests command in the doc of suites in
docker-integration-testsmodule to avoid broader scans.Why are the changes needed?
Refine docs.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA and manual checks.
Was this patch authored or co-authored using generative AI tooling?
No.