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
[7.x] Unmute more memory-related tests after the fix in #68542 #68741
Conversation
I think there was a problem with the workaround, so these tests will probably fail if unmuted. The Java security manager blocks reading |
Ah, thanks for pointing that out, @droberts195. |
@droberts195, I opened #68742 to address the security manager issue. |
#68742 has been merged and the previously failing test on the debian8 platform passed, so I think this PR is clear to be reviewed. |
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, one minor nit
@@ -8,15 +8,8 @@ | |||
|
|||
package org.elasticsearch.monitor.os; | |||
|
|||
import static org.hamcrest.Matchers.allOf; | |||
import static org.hamcrest.Matchers.anyOf; |
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 import changes are not needed for this change, 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.
The commit that muted these tests (09f823b) moved the import statements out of the standard ordering that we use, so I just restored the original standard ordering as part of the un-mute.
Relates to #68542