[ https://issues.apache.org/jira/browse/MAPREDUCE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445896#comment-13445896 ]
Hudson commented on MAPREDUCE-4569: ----------------------------------- Integrated in Hadoop-Hdfs-trunk #1151 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1151/]) MAPREDUCE-4569. Fixed TestHsWebServicesJobsQuery to pass on JDK7 by not depending on test order. Contributed by Thomas Graves. (Revision 1379146) Result = FAILURE vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1379146 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/test/java/org/apache/hadoop/mapreduce/v2/hs/webapp/TestHsWebServicesJobsQuery.java > TestHsWebServicesJobsQuery fails on jdk7 > ---------------------------------------- > > Key: MAPREDUCE-4569 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4569 > Project: Hadoop Map/Reduce > Issue Type: Bug > Affects Versions: 0.23.3, 3.0.0, 2.2.0-alpha > Reporter: Thomas Graves > Assignee: Thomas Graves > Labels: java7 > Fix For: 0.23.3, 3.0.0, 2.2.0-alpha > > Attachments: MAPREDUCE-4569.patch > > > 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. -- 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