[
https://issues.apache.org/jira/browse/MAPREDUCE-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730803#comment-13730803
]
Hudson commented on MAPREDUCE-5446:
-----------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1510 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1510/])
MAPREDUCE-5446. TestJobHistoryEvents and TestJobHistoryParsing have race
conditions. Contributed by Jason Lowe. (kihwal:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1510581)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/MRApp.java
> TestJobHistoryEvents and TestJobHistoryParsing have race conditions
> -------------------------------------------------------------------
>
> Key: MAPREDUCE-5446
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5446
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, test
> Affects Versions: 2.1.0-beta
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Fix For: 3.0.0, 2.1.1-beta
>
> Attachments: MAPREDUCE-5446.patch
>
>
> TestJobHistoryEvents and TestJobHistoryParsing are not properly waiting for
> MRApp to finish. Currently they are polling the service state looking for
> Service.STATE.STOPPED, but the service can appear to be in that state
> *before* it is fully stopped. This causes tests to finish with MRApp threads
> still in-flight, and those threads can conflict with subsequent tests when
> they collide in the filesystem.
--
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
