[
https://issues.apache.org/jira/browse/OOZIE-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248672#comment-16248672
]
Peter Cseh commented on OOZIE-3105:
-----------------------------------
This test passes in some jenkins runs and fails on others.
When the returned value is null then something is wrong and the test should
fail. The issue is that we don't know what causes this.
I've messed around with this test a bit and found that the removal of
testSamplers() makes testJMXInstrumentation() fail. From this point I'd suggest
to look into testSamplers and find out what part is required for the other test
to run successfully.
> 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: Sub-task
> 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)
