[ 
https://issues.apache.org/jira/browse/YARN-10553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ahmed Hussein updated YARN-10553:
---------------------------------
    Description: 
TestDistributedShell has grown so large over time. It has 29 tests.
 This is running the risk of exceeding 30 minutes limit for a single unit class.
 * The implementation has lots of code redundancy.
 * The Jira splits TestDistributedShell into three different unitTest for each 
TimeLineVersion: V1.0, 1.5, and 2.0
 * Fixes the broken test {{testDSShellWithEnforceExecutionType}}

  was:
TestDistributedShell has grown so large over time. It has 29 tests.
This is ru inning the risk of exceeding 30 minutes limit for a single unit 
class.

* The implementation has lots of code redundancy.
* It is inefficient in the setup and tearing down. The large percentage of time 
execution is exhausted by starting cluster and stopping the services.



> Refactor TestDistributedShell
> -----------------------------
>
>                 Key: YARN-10553
>                 URL: https://issues.apache.org/jira/browse/YARN-10553
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: distributed-shell, test
>            Reporter: Ahmed Hussein
>            Assignee: Ahmed Hussein
>            Priority: Major
>              Labels: pull-request-available, refactoring, test
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> TestDistributedShell has grown so large over time. It has 29 tests.
>  This is running the risk of exceeding 30 minutes limit for a single unit 
> class.
>  * The implementation has lots of code redundancy.
>  * The Jira splits TestDistributedShell into three different unitTest for 
> each TimeLineVersion: V1.0, 1.5, and 2.0
>  * Fixes the broken test {{testDSShellWithEnforceExecutionType}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to