Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.23.3, 3.0.0, 2.0.2-alpha
    • Fix Version/s: 0.23.3, 2.0.2-alpha
    • Component/s: None
    • Labels:

      Description

      TestHsWebServicesJobsQuery fails on jdk7 due to the test order no longer being constant.

      testJobsQueryStateNone(org.apache.hadoop.mapreduce.v2.hs.webapp.TestHsWebServicesJobsQuery) Time elapsed: 0.279 sec <<< FAILURE!
      java.lang.AssertionError: jobs is not null expected:<null> but was:<{"job":[

      {"startTime":1345559717819,"finishTime":1345560891194,"id":"job_1345560632472_0002","name":"RandomWriter","queue":"mockqueue","user":"mock","state":"KILL_WAIT","mapsTotal":0,"mapsCompleted":0,"reducesTotal":1,"reducesCompleted":1}

      ]}>
      at org.junit.Assert.fail(Assert.java:91)
      at org.junit.Assert.failNotEquals(Assert.java:645)
      at org.junit.Assert.assertEquals(Assert.java:126)
      at org.apache.hadoop.mapreduce.v2.hs.webapp.TestHsWebServicesJobsQuery.testJobsQueryStateNone(TestHsWebServicesJobsQuery.java:226)

      It looks like the issues is that the mock jobs just iterate through the JOBSTATE and since other tests run first we just happen to hit the state KILL_WAIT that we don't expect any jobs to be in.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Thomas Graves
            Reporter:
            Thomas Graves
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development