[
https://issues.apache.org/jira/browse/MAPREDUCE-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-3248:
-----------------------------------------------
Attachment: MAPREDUCE-3248-20111024.txt
It is caused by both MAPREDUCE-3199 and MAPREDUCE-3003. Once the parent
artifact for all the modules got changed to hadoop-project via MAPREDUCE-3003,
most of the mapreduce/yarn modules lost hold of the log4j configuration.
MAPREDUCE-3199 worsened it for every module.
The attached patch should work.
The alternative is to set the hard-coded location of log4j.properties in each
module, which won't be maintainable. Even relative links like
maven.project.parent.* also break over time as was found after MAPREDUCE-3003.
> Log4j logs from unit tests are lost
> -----------------------------------
>
> Key: MAPREDUCE-3248
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3248
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
> Affects Versions: 0.24.0
> Reporter: Arun C Murthy
> Priority: Blocker
> Fix For: 0.24.0
>
> Attachments: MAPREDUCE-3248-20111024.txt
>
>
> Can't find log4j logs in tests, all of them complain:
> {noformat}
> log4j:WARN No appenders could be found for logger
> (org.apache.hadoop.yarn.server.resourcemanager.security.TestDelegationTokenRenewer).
> log4j:WARN Please initialize the log4j system properly.
> {noformat}
> I suspect MAPREDUCE-3199.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
