[
https://issues.apache.org/jira/browse/MAPREDUCE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785974#action_12785974
]
Hadoop QA commented on MAPREDUCE-118:
-------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12426883/patch-118.txt
against trunk revision 887135.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 18 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-h6.grid.sp2.yahoo.net/290/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/290/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/290/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/290/console
This message is automatically generated.
> Job.getJobID() will always return null
> --------------------------------------
>
> Key: MAPREDUCE-118
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-118
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.20.1
> Reporter: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.2
>
> Attachments: patch-118-0.20.txt, patch-118-0.21.txt, patch-118.txt
>
>
> JobContext is used for a read-only view of job's info. Hence all the readonly
> fields in JobContext are set in the constructor. Job extends JobContext. When
> a Job is created, jobid is not known and hence there is no way to set JobID
> once Job is created. JobID is obtained only when the JobClient queries the
> jobTracker for a job-id., which happens later i.e upon job submission.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.