[
https://issues.apache.org/jira/browse/MAPREDUCE-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860346#action_12860346
]
Hadoop QA commented on MAPREDUCE-1612:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12442668/MR-1619-1.patch
against trunk revision 937201.
+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 failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/132/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/132/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/132/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/132/console
This message is automatically generated.
> job conf file is not accessible from job history web page
> ---------------------------------------------------------
>
> Key: MAPREDUCE-1612
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1612
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.22.0
> Reporter: Ravi Gummadi
> Assignee: Ravi Gummadi
> Fix For: 0.22.0
>
> Attachments: jobconf_history_jsp.fix.20S.patch, MR-1619-1.patch
>
>
> Clicking on conf file link from job history web page is causing an NPE if
> history file(and the job conf file) are stored on DFS. This NPE is from
> jobconf_history.jsp because jobConf built from path on DFS is not having any
> properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
