You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Mariia Mykhailova (JIRA)" <ji...@apache.org> on 2017/01/09 19:29:58 UTC

[jira] [Created] (REEF-1694) Add capability of test result verification for .NET tests on Yarn

Mariia Mykhailova created REEF-1694:
---------------------------------------

             Summary: Add capability of test result verification for .NET tests on Yarn
                 Key: REEF-1694
                 URL: https://issues.apache.org/jira/browse/REEF-1694
             Project: REEF
          Issue Type: Sub-task
          Components: REEF.NET
            Reporter: Mariia Mykhailova


To be able to run our .NET scenario tests on Yarn, we need to come up with a way to extract results of job execution from the cluster and analyze them to verify that job behavior matched our expectations. 

One possibility it to stick to the same approach as for local tests. In .NET tests on local runtime we're reading logs written by driver (and sometimes by evaluator) for this purpose. On Yarn we could use {{yarn application -status}} to check whether the job is still running and {{yarn logs}} to extract the logs once the job is completed. This has the benefit of keeping our Yarn tests verification as close to the local tests as possible.

Another option is to use an approach similar to {{TestBridgeClient}} to await for the job completion (use driver http endpoint returned by job submission). We'd still need to read logs to verify the results.

We should also introduce some timeout to the tests, and kill the submitted job using {{yarn application -kill}} once the test has timed out, to avoid overloading the cluster with our (potentially broken) tests.



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