[
https://issues.apache.org/jira/browse/HADOOP-9924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757130#comment-13757130
]
Hadoop QA commented on HADOOP-9924:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12601238/HADOOP-9924-4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The following test timeouts occurred in
hadoop-common-project/hadoop-common:
org.apache.hadoop.ipc.TestIPC
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3056//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3056//console
This message is automatically generated.
> FileUtil.createJarWithClassPath() does not generate relative classpath
> correctly
> --------------------------------------------------------------------------------
>
> Key: HADOOP-9924
> URL: https://issues.apache.org/jira/browse/HADOOP-9924
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.1.0-beta, 0.23.9
> Reporter: shanyu zhao
> Assignee: shanyu zhao
> Attachments: HADOOP-9924-2.patch, HADOOP-9924-3.patch,
> HADOOP-9924-4.patch, HADOOP-9924.patch
>
>
> On Windows, FileUtil.createJarWithClassPath() is called to generate a
> manifest jar file to pack classpath - to avoid the problem of classpath being
> too long.
> However, the relative classpath is not handled correctly. It relies on Java's
> File(relativePath) to resolve the relative path. But it really should be
> using the given pwd parameter to resolve the relative path.
> To reproduce this bug, you can try some pig job on Windows, it will fail and
> the pig log on the application master will look like this:
> 2013-08-29 23:25:55,498 INFO [main]
> org.apache.hadoop.service.AbstractService: Service
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster failed in state INITED; cause:
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException:
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigOutputFormat
> not found
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException:
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigOutputFormat
> not found
> This is because the PigOutputFormat class is in the job.jar file but the
> classpath manifest has:
> file:/c:/apps/dist/hadoop-2.1.0-beta/bin/job.jar/job.jar
> When it really should be:
> file:/<job container folder>/job.jar/job.jar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
