You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2008/11/12 12:31:44 UTC
[jira] Assigned: (HADOOP-4639) extend JobClient.runJob(JobConf)
with the ability to take a timeout, so fail better during test runs
[ https://issues.apache.org/jira/browse/HADOOP-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran reassigned HADOOP-4639:
--------------------------------------
Assignee: Steve Loughran
> extend JobClient.runJob(JobConf) with the ability to take a timeout, so fail better during test runs
> ----------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4639
> URL: https://issues.apache.org/jira/browse/HADOOP-4639
> Project: Hadoop Core
> Issue Type: Improvement
> Components: test
> Affects Versions: 0.20.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> Tests that submit jobs via JobClient hang until they are killed if something goes wrong in the back end -JobClient does not impose limits on how long runs should take, but JUnit does. If we had an overload of runJob() that took a timeout, JobClient could kill a job that was taking too long, extracting the stack trace and better diagnostics to the test reports.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.