You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "sonali shrivastava (JIRA)" <ji...@apache.org> on 2016/09/08 08:32:22 UTC

[jira] [Created] (OOZIE-2665) Non-consistent failures in Apache Oozie Core

sonali shrivastava created OOZIE-2665:
-----------------------------------------

             Summary: Non-consistent failures in Apache Oozie Core
                 Key: OOZIE-2665
                 URL: https://issues.apache.org/jira/browse/OOZIE-2665
             Project: Oozie
          Issue Type: Test
          Components: core
    Affects Versions: 4.2.0
         Environment: openjdk 1.7,apache maven 3.3.9
            Reporter: sonali shrivastava



Hi Team,

I am triggering Test for "Oozie" version 4.2.0 on RHEL ppc64le architecture using jdk 1.7 and apache maven 3.3.9 and getting inconsistent failures each time when triggered Test for Oozie-Core module.

Test Command:
mvn -Dhadoop.version=<hadoop version i.e. 2.7.1> -Phadoop-2 -Dhbase.version=1.1.2 -Dtez.version=0.7.1-SNAPSHOT -Dpig.version=0.15.1 -Dsqoop.version=1.4.6 -Dhive.version=1.2.1 -Dpig.classifier=h2 test



Please find below list for reference:

When ran test 1st time, got below failures:
Failed tests:   testAdminInstrumentation(org.apache.oozie.client.TestOozieCLI)
  testBundleStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService): expected:<RUNNINGWITHERROR> but was:<RUNNING>
  testCoordStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService): expected:<RUNNINGWITHERROR> but was:<RUNNING>
  testBundleStatusCoordSubmitFails(org.apache.oozie.service.TestStatusTransitService): expected:<FAILED> but was:<RUNNING>
  testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService): expected:<RUNNING> but was:<FAILED>
  testStreamLog(org.apache.oozie.util.TestLogStreamer): expected:<7> but was:<1>
Tests run: 1536, Failures: 6, Errors: 0, Skipped: 2



2nd time Test Results:
Failed tests:   testAdminInstrumentation(org.apache.oozie.client.TestOozieCLI)
   testCoordStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService): expected:<RUNNINGWITHERROR> but was:<RUNNING>
  testStreamLog(org.apache.oozie.util.TestLogStreamer): expected:<7> but was:<1>
  testRequeueOnException(org.apache.oozie.command.coord.TestCoordPushDependencyCheckXCommand)
Tests run: 1536, Failures: 4, Errors: 0, Skipped: 2





After applying patch to solve one of the above Test failure"testRequeueOnException",

Applied patch:"https://issues.apache.org/jira/secure/attachment/12764540/OOZIE-2379.001.patch"


1st Time Re-Test Result after applying above patch, got 3 Test failures:
Failed tests:   testForNoDuplicates(org.apache.oozie.event.TestEventGeneration): expected:<2> but was:<1>
  testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService): expected:<RUNNING> but was:<FAILED>
  testStreamLog(org.apache.oozie.util.TestLogStreamer): expected:<7> but was:<1>




2nd time Re-Test Result after applying patch above,got 5 test failures:
Failed tests:   testBundleStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService): expected:<RUNNINGWITHERROR> but was:<RUNNING>
  testCoordStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService): expected:<RUNNINGWITHERROR> but was:<RUNNING>
  testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService): expected:<RUNNING> but was:<FAILED>
  testMaxMatThrottleNotPicked(org.apache.oozie.service.TestCoordMaterializeTriggerService): expected:<Wed Sep 07 15:32:28 IST 2016> but was:<Wed Sep 07 15:32:42 IST 

2016>
  testStreamLog(org.apache.oozie.util.TestLogStreamer): expected:<7> but was:<1>
Tests run: 1536, Failures: 5, Errors: 0, Skipped: 2



3rd Time Re-Test Result after applying above patch, got 3 Test failures:
Failed tests:   testBundleStatusCoordSubmitFails(org.apache.oozie.service.TestStatusTransitService): expected:<FAILED> but was:<RUNNING>
  testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService): expected:<RUNNING> but was:<FAILED>
  testStreamLog(org.apache.oozie.util.TestLogStreamer): expected:<7> but was:<1>
Tests run: 1536, Failures: 3, Errors: 0, Skipped: 2



As a result, I am getting different and in-consistent failures each time I trigger test.
Getting only 1 consistent failure i.e.
testStreamLog(org.apache.oozie.util.TestLogStreamer): expected:<7> but was:<1>


@Team:
Can you please tell me the reason for such in-consistent failures. Thank You.


Regards,
Sonali Shrivastava




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)