hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5005) TestProcfsProcessTree#testProcessTree() doesn't wait long enough for the process to die
Date Tue, 12 Mar 2013 01:33:17 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karthik Kambatla updated MAPREDUCE-5005:
----------------------------------------

    Attachment: mr-5005.patch

Here is a trivial patch that seems to be fixing the test:
# Added a simple loop to check if process is alive.
# Ran the test in a loop and noticed no failures.
                
> TestProcfsProcessTree#testProcessTree() doesn't wait long enough for the process to die
> ---------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5005
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5005
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.0.2-alpha
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: mr-5005.patch
>
>
> TestProcfsProcessTree#testProcessTree fails occasionally with the following stack trace
> {noformat}
> Stack Trace:
> junit.framework.AssertionFailedError: expected:<false> but was:<true>
>         at org.apache.hadoop.util.TestProcfsBasedProcessTree.testProcessTree(TestProcfsBasedProcessTree.java)
> {noformat}
> kill -9 is executed asynchronously, the signal is delivered when the process comes out
of the kernel (sys call). Checking if the process died immediately after can fail at times.

--
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

Mime
View raw message