[
https://issues.apache.org/jira/browse/OOZIE-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227373#comment-16227373
]
Peter Bacsko edited comment on OOZIE-3105 at 10/31/17 7:35 PM:
---------------------------------------------------------------
[~dbist13] thanks for taking care of this. Recently I've been thinking about
creating an umbrella JIRA that includes all flaky tests we have right now, I
wanted to include this as well. But I don't fully understand this patch, how
does using {{assumeNotNull}} instead of {{assertNotNull}} eliminate the
flakyness? It just makes JUnit skip the test, no?
was (Author: pbacsko):
[~dbist13] thanks for taking care of this. Recently I've been thinking about
creating an umbrella JIRA that includes all flaky tests we have right now, I
wanted to include this as well. But I don't fully understand this patch, how
does using {{assumeNotNull}} instead of {{assertNotNull}} eliminate the
flakyness?
> 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)
