jmx metrics: Add test timeouts and mbean server status assertions #218
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Some builds are taking exceedingly long and this appears to be based on platform mbean connector server access flake:
These changes add 10s timeouts to all suites w/ mbean server tests and an assertion before each test that the server is active, which is said to reflect the connector status though I wasn't able to verify this directly. Hopefully they will provide more information about the underlying issue.