Andreas Grüninger 2013-10-10, 07:33
for hadoop 2.x, the log4j. properties file for each project should be in
but there's a risk that tests in sub projects that include
hadoop-commons-test.jar (or other -test JARs, like hadoop-hdfs) may pick up
the version in the test jar ahead of any one that they have locally -so try
to add the debug option in the test resources of the base -common and -hdfs
On 10 October 2013 08:33, "Andreas Grüninger" <[EMAIL PROTECTED]> wrote:
> I compiled the native libraries of 2.1.1 for OpenIndiana.
> When I run the tests to check my changes I get a lot of errors.
> When I run the tests without my changes I get nearly the same errors.
> I checked the tests with the current stable 1.2.1 too with/without native
> And I get there errors too, about 29 of 1522 (by heart, sitting at home).
> The inspection of the crash reports let me assume that there are errors
> the usage of fstat and IPC errors.
> Maybe some of you compile the source with OI or Solaris and can give some
> hints how to compile it. The compiler is gcc 4.6.2.
> I found the crash reports and the logs in build/test/....
> But I did not understand which log4j.properties must be changed to get
> DEBUG level information. And where to find it afterwards. I assume the same
> log files which now contains the log messages from log4j with debug level
> INFO. I found log4j.properties, changed to DEBUG, recompiled and repeated
> the tests, but to no avail.
> I would really like to change the source code but I need the logging of
> the DEBUG messages.
> TIA and Greetings
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Colin McCabe 2013-10-10, 20:08