You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2013/12/24 01:45:50 UTC

[jira] [Created] (OOZIE-1657) TestCoordPushDependencyCheckXCommand.testTimeOutWithUnresolvedMissingDependencies is flakey

Robert Kanter created OOZIE-1657:
------------------------------------

             Summary: TestCoordPushDependencyCheckXCommand.testTimeOutWithUnresolvedMissingDependencies is flakey
                 Key: OOZIE-1657
                 URL: https://issues.apache.org/jira/browse/OOZIE-1657
             Project: Oozie
          Issue Type: Bug
          Components: tests
    Affects Versions: trunk
            Reporter: Robert Kanter


{{TestCoordPushDependencyCheckXCommand.testTimeOutWithUnresolvedMissingDependencies}} appears to be flakey as I've seen it fail a few times here and there on test-patch and locally.  

{noformat}
junit.framework.ComparisonFailure: expected:<...dt=20120430;country=[]uk> but was:<...dt=20120430;country=[brazil#hcat://localhost:30034/default/tablename/dt=20120430;country=usa#hcat://localhost:30034/default/tablename/dt=20120430;country=]uk>
	at junit.framework.Assert.assertEquals(Assert.java:85)
	at junit.framework.Assert.assertEquals(Assert.java:91)
	at org.apache.oozie.command.coord.TestCoordPushDependencyCheckXCommand.checkDependencies(TestCoordPushDependencyCheckXCommand.java:459)
	at org.apache.oozie.command.coord.TestCoordPushDependencyCheckXCommand.testTimeOutWithUnresolvedMissingDependencies(TestCoordPushDependencyCheckXCommand.java:273)
	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}
https://builds.apache.org/job/oozie-trunk-precommit-build/964/testReport/junit/org.apache.oozie.command.coord/TestCoordPushDependencyCheckXCommand/testTimeOutWithUnresolvedMissingDependencies/



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)