hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Daley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5001) Junit tests that time out don't write any test progress related logs
Date Fri, 09 Jan 2009 18:11:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662455#action_12662455
] 

Nigel Daley commented on HADOOP-5001:
-------------------------------------

Ya, this is more of an Ant Junit problem.  I suggest we close this.  The workaround is to
run with -Dtest.output=yes so that output goes to the console.  We do exactly this on Hudson
builds so that timeout tests can be seen in the console log (which as a result is > 40
MB).

> Junit tests that time out don't write any test progress related logs
> --------------------------------------------------------------------
>
>                 Key: HADOOP-5001
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5001
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: test
>            Reporter: Vinod K V
>            Assignee: Vinod K V
>
> Some junit tests time out frequently possibly because of a bug. When such tests time
out, the log4j appender isn't writing anything to the log files. It seems that all the log
statements  are buffered in the memory till test completion. The logs get written to the log
file only after the test goes to completion.
> This is seriously limiting debugging in presence of a test time out. *If* possible, we
should try to flush logs regularly so that we can find out the extent to which a test has
progressed before timing out.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message