[To dev/1.3] Exclude all AINode (AIClusterIT) integration tests from the build#17982
Open
CRZbulabula wants to merge 1 commit into
Open
[To dev/1.3] Exclude all AINode (AIClusterIT) integration tests from the build#17982CRZbulabula wants to merge 1 commit into
CRZbulabula wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev/1.3 #17982 +/- ##
==========================================
Coverage 42.54% 42.54%
Complexity 241 241
==========================================
Files 3622 3622
Lines 241226 241226
Branches 29396 29396
==========================================
+ Hits 102629 102633 +4
+ Misses 138597 138593 -4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
CRZbulabula
changed the title
CRZbulabula
force-pushed
the
ignore-ainode-tests
branch
from
efa5a92 to
95a00e7
Compare
AINode integration tests are temporarily disabled at the build and CI level, without touching any test source code: - integration-test/pom.xml: add the AIClusterIT category to excludedGroups in the AIClusterIT profile. includedGroups is kept so the profile stays scoped to the AINode tests only; excludedGroups takes precedence over includedGroups in maven-failsafe, so no AINode test is executed even when the profile is activated. - .github/workflows/cluster-it-1c1d1a.yml: remove the "Cluster IT - 1C1D1A / AINode" workflow. Its only job built AINode and ran the AIClusterIT integration tests, so it is no longer needed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
CRZbulabula
force-pushed
the
ignore-ainode-tests
branch
from
95a00e7 to
49927c1
Compare
|
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
1 participant
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
Disable all AINode-related integration tests at the build level (by JUnit
category) instead of annotating each test with
@Ignore.Why
We want to temporarily stop running the AINode integration tests without
touching the test source code, so they can be re-enabled with a one-line
revert later.
How
AINodeBasicITis the only AINode test class and it is annotated with@Category({AIClusterIT.class}). TheAIClusterITMaven profile inintegration-test/pom.xmlis the only entry point that runs this category(every other IT profile includes only its own categories, so they never
pick up AINode tests).
This PR adds the
AIClusterITcategory tointegrationTest.excludedGroupsin that profile. In maven-failsafe,
excludedGroupstakes precedence overincludedGroups, so even when theAIClusterITprofile is activated, noAINode test is executed.
Scope
integration-test/pom.xml—AIClusterITprofile only🤖 Generated with Claude Code