[jira] [Commented] (REEF-1271) Add better test reporting APIs to REEF.NET

["Andrey (JIRA)" <ji...@apache.org>]

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

Andrey commented on REEF-1271:
------------------------------

yes, relying on logging is cumbersome as logging can change potentially failing lots of tests. I am assuming you are referring to plumbing to report evaluator/task execution status as part of Job details? so that Test could check Job Status details to find what failures/retries occurred during job execution.


> Add better test reporting APIs to REEF.NET
> ------------------------------------------
>
>                 Key: REEF-1271
>                 URL: https://issues.apache.org/jira/browse/REEF-1271
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF.NET, Tests
>            Reporter: Markus Weimer
>
> REEF.NET currently relies on parsing Driver and Evaluator logs to determine whether a functional (integration) test passed. The test puts a specific message into the log, which is parsed after the Driver finishes. 
> This works OK for tests on the local runtime, but is undesirable for tests on clusters. On the Java side, we rely on REEF's forwarding of exceptions from the Evaluator to the Driver and the Driver to the Client: A test indicates failure by throwing {{DriverSideFailure}} or {{EvaluatorSideFailure}} exceptions.



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