hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4913) TestMRAppMaster#testMRAppMasterMissingStaging occasionally exits
Date Sat, 05 Jan 2013 03:30:13 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544559#comment-13544559

Hadoop QA commented on MAPREDUCE-4913:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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/3203//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3203//console

This message is automatically generated.
> TestMRAppMaster#testMRAppMasterMissingStaging occasionally exits
> ----------------------------------------------------------------
>                 Key: MAPREDUCE-4913
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4913
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am
>    Affects Versions: 2.0.3-alpha, 0.23.6
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: MAPREDUCE-4913.patch
> testMRAppMasterMissingStaging will sometimes cause the JVM to exit due to this error
from AsyncDispatcher:
> {noformat}
> 2013-01-05 02:14:54,682 FATAL [AsyncDispatcher event handler] event.AsyncDispatcher (AsyncDispatcher.java:dispatch(137))
- Error in dispatcher thread
> java.lang.Exception: No handler for registered for class org.apache.hadoop.mapreduce.jobhistory.EventType,
cannot deliver EventType: AM_STARTED
>         at org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:132)
>         at org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:77)
>         at java.lang.Thread.run(Thread.java:662)
> 2013-01-05 02:14:54,682 INFO  [AsyncDispatcher event handler] event.AsyncDispatcher (AsyncDispatcher.java:dispatch(140))
- Exiting, bbye..
> {noformat}
> This can cause a build to fail since the test process exits without unregistering from
surefire which treats it as a build error rather than a test failure.

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

View raw message