[
https://issues.apache.org/jira/browse/YARN-10927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Domok resolved YARN-10927.
--------------------------------
Resolution: Won't Fix
Some improvements has been made for the TestCapacityScheduler class in the
following Jira items:
* YARN-10960
* YARN-10961
* YARN-10962
* YARN-10963
These old test cases are not easy to read, but imho not the assertions are the
root cause, a re-write or complete refactor would be needed, but that would
take too much time. Closing this task as won't fix.
> Explain assertion literals in testcases of CapacityScheduler and related test
> classes
> -------------------------------------------------------------------------------------
>
> Key: YARN-10927
> URL: https://issues.apache.org/jira/browse/YARN-10927
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Szilard Nemeth
> Assignee: Tamas Domok
> Priority: Minor
>
> In the existing tests the assertion literals could be explained for easier
> understanding As there are too many test classes, we can tackle this more
> easily in a feature by feature fashion
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
