[
https://issues.apache.org/jira/browse/HADOOP-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558551#action_12558551
]
Hadoop QA commented on HADOOP-2570:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12373016/HADOOP-2570_1_20080112.patch
against trunk revision r611734.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests -1. The patch failed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1578/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1578/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1578/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1578/console
This message is automatically generated.
> streaming jobs fail after HADOOP-2227
> -------------------------------------
>
> Key: HADOOP-2570
> URL: https://issues.apache.org/jira/browse/HADOOP-2570
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/streaming
> Affects Versions: 0.15.2
> Reporter: lohit vijayarenu
> Assignee: Amareshwari Sri Ramadasu
> Priority: Blocker
> Fix For: 0.15.3
>
> Attachments: HADOOP-2570_1_20080112.patch, patch-2570.txt
>
>
> HADOOP-2227 changes jobCacheDir. In streaming, jobCacheDir was constructed
> like this
> {code}
> File jobCacheDir = new File(currentDir.getParentFile().getParent(), "work");
> {code}
> We should change this to get it working. Referring to the changes made in
> HADOOP-2227, I see that the APIs used in there to construct the path are not
> public. And hard coding the path in streaming does not look good. thought?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
