You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2016/03/08 01:37:40 UTC

[jira] [Created] (BEAM-98) Travis coverage broken due to too much logging

Davor Bonaci created BEAM-98:
--------------------------------

             Summary: Travis coverage broken due to too much logging
                 Key: BEAM-98
                 URL: https://issues.apache.org/jira/browse/BEAM-98
             Project: Beam
          Issue Type: Bug
          Components: runner-flink
            Reporter: Davor Bonaci
            Assignee: Maximilian Michels
            Priority: Minor


Travis error:
{@code}
The log length has exceeded the limit of 4 Megabytes (this usually means that test suite is raising the same exception over and over).

The build has been terminated.
{@code}

Most output comes from the 'verify' phase from the Flink runner.

Max, is this something that you could potentially tackle?



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