-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add internalClusterTest to check task #53444
Conversation
This commit adds internalClusterTest in xpack core to run as part of check. This was accidentally removed in a refactoring. Other xpack modules already do this, but core was left out. This commit also mutes 2 tests that currently fail. closes elastic#53407
Pinging @elastic/es-core-infra (:Core/Infra/Build) |
@@ -53,6 +54,7 @@ | |||
import static org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertHitCount; | |||
|
|||
@ESIntegTestCase.ClusterScope(numDataNodes = 0) | |||
@LuceneTestCase.AwaitsFix(bugUrl = "https://github.com/elastic/elasticsearch/issues/53442") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this test has been fixed. The AwaitsFix can be removed here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Although I'm wondering if we should do something more generic like check.dependsOn tasks.withType(Test)
in BuildPlugin
. We'd have to make some exceptions for things like packaging tests and BWC. Perhaps somethign in the testing conventions plugin to freak out if there's a Test
task that no other task depends on? That might be difficult to do though in a way that doesn't completely destroy lazy task configuration.
I agree we should look at other ways to make this more robust, but I think that is beyond the scope of this PR, which is simply to re-enable these tests as they are now. Let's follow up within the build area to see how we can better model these tests in gradle. |
This commit adds internalClusterTest in xpack core to run as part of check. This was accidentally removed in a refactoring. Other xpack modules already do this, but core was left out. This commit also mutes 2 tests that currently fail. closes #53407
This commit adds internalClusterTest in xpack core to run as part of check. This was accidentally removed in a refactoring. Other xpack modules already do this, but core was left out. This commit also mutes 2 tests that currently fail. closes #53407
This commit adds internalClusterTest in xpack core to run as part of
check. This was accidentally removed in a refactoring. Other xpack
modules already do this, but core was left out. This commit also mutes 2
tests that currently fail.
closes #53407