[
https://issues.apache.org/jira/browse/OOZIE-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660086#comment-13660086
]
Rohini Palaniswamy commented on OOZIE-1298:
-------------------------------------------
No. That should not be a problem. If the test still fails with +100ms, then
need to investigate.
> TestPartitionDependencyManagerEhcache.testEvictionOnTimeToIdle is flakey
> ------------------------------------------------------------------------
>
> Key: OOZIE-1298
> URL: https://issues.apache.org/jira/browse/OOZIE-1298
> Project: Oozie
> Issue Type: Bug
> Components: tests
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Rohini Palaniswamy
> Fix For: trunk
>
> Attachments: OOZIE-1298.patch
>
>
> This test looks flakey; I've seen it fail on a number of test-patch builds.
> e.g.
> https://builds.apache.org/job/oozie-trunk-precommit-build/410/testReport/junit/org.apache.oozie.service/TestPartitionDependencyManagerEhcache/testEvictionOnTimeToIdle/
> {noformat}
> junit.framework.AssertionFailedError: Expected: <null> but was: [0]
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertNull(Assert.java:237)
> at junit.framework.Assert.assertNull(Assert.java:230)
> at
> org.apache.oozie.service.TestPartitionDependencyManagerEhcache.testEvictionOnTimeToIdle(TestPartitionDependencyManagerEhcache.java:82)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at
> org.apache.maven.surefire.junitcore.ClassDemarcatingRunner.run(ClassDemarcatingRunner.java:58)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
