[
https://issues.apache.org/jira/browse/OOZIE-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227428#comment-16227428
]
Artem Ervits commented on OOZIE-3105:
-------------------------------------
[~pbacsko] you're correct, except in the old behavior we just failed
indefinitely and if value was null, assertion would fail and throw an error
that JMX service is unavailable. I may have introduced wrong behavior but test
only fails due to null value. We can move the assertion back after the catch
but it won't fix the failure. Again, I'm happy to work on this with some
direction.
> testJMXInstrumentation from the
> org.apache.oozie.util.TestMetricsInstrumentation class is flaky
> -----------------------------------------------------------------------------------------------
>
> Key: OOZIE-3105
> URL: https://issues.apache.org/jira/browse/OOZIE-3105
> Project: Oozie
> Issue Type: Bug
> Components: tests
> Affects Versions: 4.3.0
> Environment: mvn: 3.5.0
> java: 1.8.0.144
> Reporter: Artem Ervits
> Assignee: Artem Ervits
> Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-3105-00.patch
>
>
> I'm able to reproduce the test failure consistently by running test in
> isolation with the following command
> {code}
> mvn clean
> -Dtest=org.apache.oozie.util.TestMetricsInstrumentation#testJMXInstrumentation
> test
> {code}
> the test succeeds consistently with the following
> {code}
> mvn clean -Dtest=org.apache.oozie.util.TestMetricsInstrumentation test
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
