Skip hybrid IT cases in premerge [fast-ut] [reduced-it] [databricks] - #15421
Draft
res-life wants to merge 1 commit into
Draft
Skip hybrid IT cases in premerge [fast-ut] [reduced-it] [databricks]#15421res-life wants to merge 1 commit into
res-life wants to merge 1 commit into
Conversation
Signed-off-by: Chong Gao <chongg@nvidia.com>
Collaborator
Author
|
build |
Collaborator
Author
|
build |
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.
Contributes to #15404.
Description
Problem
Premerge invokes the Hybrid execution IT suite separately even though the nightly/default IT path already covers it. The invocation takes approximately 2 minutes 48 seconds, and reduced-IT selection only lowers the collected cases from 314 to 252 (19.7%). This makes case reduction ineffective for this scenario.
Change
Remove the Hybrid setup and
hybrid_testinvocation frommvn_verifyinjenkins/spark-premerge-build.sh. Test definitions and the nightly test path are unchanged.Impact
Premerge no longer spends approximately 2 minutes 48 seconds on this scenario. Hybrid execution remains fully covered by nightly CI, and developers can still run it explicitly with
TEST_MODE=HYBRID_EXECUTION. There is no user-facing behavior change.Validation
bash -n jenkins/spark-premerge-build.shgit diff --checkhybrid_testsuite still runs fromjenkins/spark-tests.shforDEFAULTandHYBRID_EXECUTIONChecklists
Documentation
Testing
(
hybrid_testremains in nightlyDEFAULTand explicitHYBRID_EXECUTIONmodes.)Performance