-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Move systemPropertiesOverrideTest to separate source set
#137492
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
Move systemPropertiesOverrideTest to separate source set
#137492
Conversation
Today `:server:systemPropertiesOverrideTest` uses the same source set as `:server:test`, but runs a disjoint set of tests via includes & excludes. This forces every developer to choose in their IDE between the two tasks when running any unit test in `:server` even though there's only one appropriate task to run for any particular test. This commit moves the serverless-specific unit tests into their own source set to remove this friction in the development flow.
|
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
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
Thanks for improving this!
|
|
||
| tasks.named("test").configure { | ||
| systemProperty 'es.stateless.allow.index.refresh_interval.override', 'true' | ||
| // systemProperty 'es.serverless_transport', 'true' |
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.
We still need this, right? I wonder why the CI didn't fail?
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.
These tests relate to system properties set only in serverless Elasticsearch so there's no need for them in the `8.19` branch. Moreover, as with elastic#137492, this extra Gradle task forces every developer to make an extra choice when running tests in `:server`. This commit removes the unnecessary tests and the corresponding Gradle task.
These tests relate to system properties set only in serverless Elasticsearch so there's no need for them in the `8.19` branch. Moreover, as with #137492, this extra Gradle task forces every developer to make an extra choice when running tests in `:server`. This commit removes the unnecessary tests, the corresponding Gradle task, and the now-untested code.
Today
:server:systemPropertiesOverrideTestuses the same source set as:server:test, but runs a disjoint set of tests via includes &excludes. This forces every developer to choose in their IDE between the
two tasks when running any unit test in
:servereven though there'sonly one appropriate task to run for any particular test.
This commit moves the serverless-specific unit tests into their own
source set to remove this friction in the development flow.