[
https://issues.apache.org/jira/browse/HADOOP-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611433#action_12611433
]
Hadoop QA commented on HADOOP-3654:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12385398/hadoop-3654.patch
against trunk revision 674671.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2807/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2807/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2807/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2807/console
This message is automatically generated.
> Log4J logging of stack trace may deadlock JRockit in TestFileSystem
> -------------------------------------------------------------------
>
> Key: HADOOP-3654
> URL: https://issues.apache.org/jira/browse/HADOOP-3654
> Project: Hadoop Core
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.19.0
> Environment: Ubuntu 8.04 x86_64 4-way running java version "1.6.0_02"
> Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
> BEA JRockit(R) (build R27.4.0-90-89592-1.6.0_02-20070928-1715-linux-x86_64,
> compiled mode)
> Linux 2.6.22-15-generic #1 SMP Tue Jun 10 08:52:15 UTC 2008 x86_64 GNU/Linux
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: hadoop-3654.patch
>
>
> This is being added as a bugrep so that other people can find it, and the
> workaround
> 1. On my machine TestFileSystem will hang, even overnight -even though the
> build was set with a timeout.
> 2. halting the build left a JVM running; it was not being killed.
> 3. Under the IDE, the main thread appears hung in the native library call to
> get a stack trace, somewhere inside Log4J
> 4. the IDE could not halt the build, and could not be shut down cleanly either
> The fix for this problem was to edit conf/log4j.properties and switch to a
> log4J log pattern that did not print the line of the code
> log4j.appender.console.layout.ConversionPattern=%-4r %-5p %c %x - %m%n
> Given that working out a stack trace can be an expensive call, and that it
> can apparently hang some JVMs, perhaps it should not be the default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
