[ 
https://issues.apache.org/jira/browse/TEZ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144174#comment-14144174
 ] 

Jeff Zhang edited comment on TEZ-1568 at 9/23/14 1:36 AM:
----------------------------------------------------------

[~bikassaha] 

bq. Maybe be can move the session test to TestMRRJobsDAGApi which is already 
starting the minicluster so we can avoid that cost in this test.
I feel moving the test to TestMRRJobsDAGApi  is not a good idea. It didn't 
match the scope of  TestMRRJobsDAGApi. So I didn't move it out.

Update the patch, now the status:

* Verify the diagnostics in DAGStatus in session mode (using local mode) -- 
cost 10 seconds
* Verify the diagnostics in DAGStatus match that from Application Report in 
non-session mode (using TezMiniCluster)  -- cost 1 minute


was (Author: zjffdu):
[~bikassaha] 

bq. Maybe be can move the session test to TestMRRJobsDAGApi which is already 
starting the minicluster so we can avoid that cost in this test.
Move the test to TestMRRJobsDAGApi  will not easy to find the test in future. 
So I didn't move it out.

Update the patch, now the status:

* Verify the diagnostics in DAGStatus in session mode (using local mode) -- 
cost 10 seconds
* Verify the diagnostics in DAGStatus match that from Application Report in 
non-session mode (using TezMiniCluster)  -- cost 1 minute

> Add system test for propagation of diagnostics for errors
> ---------------------------------------------------------
>
>                 Key: TEZ-1568
>                 URL: https://issues.apache.org/jira/browse/TEZ-1568
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Jeff Zhang
>            Assignee: Jeff Zhang
>         Attachments: TEZ-1568.patch, Tez-1568-2.patch, Tez-1568-3.patch, 
> Tez-1568-4.patch, Tez-1568-5.patch
>
>
> Design system test where exception come from Input, Output, Processor, 
> InputInitializer and VertexManagerPlugin



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to