-
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
Set netty available processors system property for tests globally #75699
Set netty available processors system property for tests globally #75699
Conversation
Pinging @elastic/es-delivery (Team:Delivery) |
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 picking this up.
* We have to disable setting the number of available processors as tests in the same JVM randomize processors and will step on each | ||
* other if we allow them to set the number of available processors as it's set-once in Netty. | ||
*/ | ||
systemProperty 'es.set.netty.runtime.available.processors', 'false' |
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.
configuring this here probably didn't even make sense (as it's a YML test), right?
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.
Correct. I suspect it was just copy/pasted from elsewhere.
…cessors_sys_prop # Conflicts: # x-pack/plugin/build.gradle
…astic#75699) (cherry picked from commit 9d14bc9)
Set
es.set.netty.runtime.available.processors
system property globally inESTestCase
rather than configuring Gradle or JUnit test runners to add it. This makes for a more consistent test execution environment and alleviates issues with the IDE not being configured properly.Closes #74737