-
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
Fix XPackPlugin usages in tests #47252
Fix XPackPlugin usages in tests #47252
Conversation
XPackPlugin holds data in statics and can only be initialized once. This caused tests to fail primarily when running with a low max-workers. Replaced usages with the LocalStateCompositeXPackPlugin, which handles this properly for testing.
Pinging @elastic/es-search |
Example build failure:
|
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.
Makes sense, LGTM.
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.
Thanks for fixing this!
XPackPlugin holds data in statics and can only be initialized once. This caused tests to fail primarily when running with a low max-workers. Replaced usages with the LocalStateCompositeXPackPlugin, which handles this properly for testing.
XPackPlugin holds data in statics and can only be initialized once. This caused tests to fail primarily when running with a low max-workers. Replaced usages with the LocalStateCompositeXPackPlugin, which handles this properly for testing.
XPackPlugin holds data in statics and can only be initialized once. This
caused tests to fail primarily when running with a low max-workers.
Replaced usages with the LocalStateCompositeXPackPlugin, which handles
this properly for testing.