[
https://issues.apache.org/jira/browse/HADOOP-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662419#action_12662419
]
Steve Loughran commented on HADOOP-5001:
----------------------------------------
this is probably a result of the way Ant's (classic) XML logger buffers the
entire doc in memory, so that it can include summary statistics in the top
level XML node.
Its failings are known, but there's no easy way to change it without breaking
the current set of CI tools (though we could go from a different XML to the
legacy XML via an XSL operation). I've proposed something XHTML-based that gets
streamed out in the past.
> 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.
