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

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

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

Markus Weimer edited comment on REEF-1271 at 10/22/17 5:02 PM:
---------------------------------------------------------------

I'm playing around with this idea [here|https://github.com/markusweimer/reef/tree/REEF-1271]. The [diff|https://github.com/apache/reef/compare/master...markusweimer:REEF-1271?expand=1] is probably the better view.


was (Author: markus.weimer):
I'm playing around with this idea [here|https://github.com/markusweimer/reef/tree/REEF-1271].

> 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
>            Priority: Critical
>
> 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.4.14#64029)