[
https://issues.apache.org/jira/browse/MAPREDUCE-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728085#comment-13728085
]
Hadoop QA commented on MAPREDUCE-5446:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595653/MAPREDUCE-5446.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3931//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3931//console
This message is automatically generated.
> 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
> 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
