beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Bonaci (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-98) Travis coverage broken due to too much logging
Date Tue, 08 Mar 2016 00:38:40 GMT

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

Davor Bonaci updated BEAM-98:
-----------------------------
    Description: 
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?

  was:
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?


> 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)

Mime
View raw message