-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Converting randomized testing to create a separate unitTest task instead of replacing the builtin test task #36311
Converting randomized testing to create a separate unitTest task instead of replacing the builtin test task #36311
Conversation
Pinging @elastic/es-core-infra |
Can you address the conflicts in x-pack/plugin/ccr/qa? We renamed some sub-projects there. |
This PR seems to have some unmerged other PRs in it, causing the diff to be around +35k lines...can you please re-ping for review when that is resolved? |
@rjernst Not sure what you mean, the diff looks normal to me |
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.
I'm not sure why github showed me a such a weird diff before; it looks fine now.
This looks fine to me. In addition to my one comment, I think the PR title needs to be changed, as it is only a side effect of the actual change: converting randomized testing to create a separate unitTest task instead of replacing the builtin test task.
it.enabled = false | ||
RandomizedTestingTask unitTest = tasks.create('unitTest', RandomizedTestingTask) | ||
unitTest.description = 'Runs unit tests with the randomized testing framework' | ||
unitTest.include("**/*Tests.class") |
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.
I think which tests are run should stay outside of RandomizedTesting code. It is still my intention to get this back into the randomizedtesting project, in which case the test naming patterns should not be assumed here.
…ead of replacing the builtin test task (#36311) - Create a separate unitTest task instead of Gradle's built in - convert all configuration to use the new task - the built in task is now disabled
Fix the typo introdcued in elastic#36311 causing CI failures with the FipsJvm.
Fix the typo introduced in #36311 causing CI failures with the FipsJvm.
Fix the typo introduced in #36311 causing CI failures with the FipsJvm.
Gradle 5.0 deprecates removing dependencies from tasks and replacing tasks with a different implementation.
This means that replacing the
test
task will be impossible for Gradle 6.0.This PR introduced a
unitTest
task instead. The originaltest
is now disabled and depended onunitTest
. This means that running./gradlew test
will work as before.With this change we will be able to continue upgrading Gradle regardless of #31496.
I also think that the
test
tasks name is too broad anyhow and probably only kept for historical reasons and because different projects split the tests differently.With this PR
test
will be much more likecheck
just a way to group other tasks together.Closes #33343