Github user gatorsmile commented on the issue:
    The test case design is pretty good. It covers all the scenarios. 
    - Could you add a check for the negative case? That means, when users do 
not provide the right TaskAssigner name, we fall back to the default round 
robin one
    - For the existing unchanged test cases in `TaskSchedulerImplSuite.scala`, 
please add a check to verify whether it picks the default one. 
    - If possible, please change one of the existing test case in 
`TaskSchedulerImplSuite.scala`, ensure that users are allowed to input the 
round robin as the task assigner.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to