reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (REEF-1331) Reduce amount of logs written by .NET tests
Date Tue, 12 Apr 2016 00:36:25 GMT

     [ https://issues.apache.org/jira/browse/REEF-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Markus Weimer resolved REEF-1331.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.15

Resolved via [#945|https://github.com/apache/reef/pull/945]

> Reduce amount of logs written by .NET tests
> -------------------------------------------
>
>                 Key: REEF-1331
>                 URL: https://issues.apache.org/jira/browse/REEF-1331
>             Project: REEF
>          Issue Type: Test
>          Components: REEF.NET
>            Reporter: Mariia Mykhailova
>            Assignee: Mariia Mykhailova
>             Fix For: 0.15
>
>
> An average AppVeyor test run produces 16k lines of logs (written by tests themselves).
Very few of them have any value in indication of test success or failure. Several offenders
which catch my eye are:
> * Log level is verbose. I'm not sure we need it in default test runs.
> * {{INFO: try open .\REEF_LOCAL_RUNTIMEe25631b8\reef-BroadcastReduceDriver-20160411174216287\driver\DriverHttpEndpoint.txt}}
followed by {{INFO: File does not exist: .\REEF_LOCAL_RUNTIMEe25631b8\reef-BroadcastReduceDriver-20160411174216287\driver\DriverHttpEndpoint.txt}}
- over a 100 entries, caused by retries to read this file while it's unavailable.
> * {{GetLogFile}} - 10-20 entries per ReefFunctionalTest just to indicate that the test
is trying to read a log.
> * several logs which log progress of typical events have log level INFO while it should
be VERBOSE.



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

Mime
View raw message