[
https://issues.apache.org/jira/browse/MAPREDUCE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403664#comment-13403664
]
Hadoop QA commented on MAPREDUCE-4355:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12533921/MR-4355_mr2.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient:
org.apache.hadoop.mapreduce.lib.jobcontrol.TestMapReduceJobControl
org.apache.hadoop.mapred.jobcontrol.TestLocalJobControl
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2530//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2530//console
This message is automatically generated.
> Add RunningJob.getJobStatus()
> -----------------------------
>
> Key: MAPREDUCE-4355
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4355
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, mrv2
> Affects Versions: 1.0.3, 2.0.0-alpha
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Fix For: 1.1.0, 2.0.1-alpha
>
> Attachments: MR-4355_mr1.patch, MR-4355_mr2.patch
>
>
> Usecase: Read the start/end-time of a particular job.
> Currently, one has to iterate through JobClient.getAllJobStatuses() and
> iterate through them. JobClient.getJob(JobID) returns RunningJob, which
> doesn't hold the job's start time.
> Adding RunningJob.getJobStatus() solves the issue.
--
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
