You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Timothy Farkas (JIRA)" <ji...@apache.org> on 2018/05/22 23:10:00 UTC
[jira] [Comment Edited] (DRILL-6437) Travis Fails Because Logs Are
Flooded.
[ https://issues.apache.org/jira/browse/DRILL-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484663#comment-16484663 ]
Timothy Farkas edited comment on DRILL-6437 at 5/22/18 11:09 PM:
-----------------------------------------------------------------
I think the solution is to use the silent option in the maven-dependency plugin when we download the mysql archive. https://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html#silent This option is not in dependency plugin version 2.8. So I will bump up the version used by the jdbc tests to 3.1.0
was (Author: timothyfarkas):
I think the solution is to use the silent option in the maven-dependency plugin when we download the mysql archive. https://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html#silent
> Travis Fails Because Logs Are Flooded.
> --------------------------------------
>
> Key: DRILL-6437
> URL: https://issues.apache.org/jira/browse/DRILL-6437
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.14.0
> Reporter: Timothy Farkas
> Assignee: Timothy Farkas
> Priority: Critical
>
> The Travis logs are flooded when downloading mysql.
> {code}
> Downloading from central: http://repo.maven.apache.org/maven2/com/jcabi/mysql-dist/5.6.14/mysql-dist-5.6.14-linux-amd64.zip
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> Progress (1): 0.1/325 MB
> {code}
> And the Travis build fails with
> {code}
> The log length has exceeded the limit of 4 MB (this usually means that the test suite is raising the same exception over and over).
> The job has been terminated
> {code}
> This doesn't happen in the core apache travis builds because dependencies are chached on Travis. However, when running a private Travis build that doesn't have dependencies cached, we have to redownload mysql and we run into this problem.
> Example Travis build with the issue: https://travis-ci.org/ilooner/drill/builds/382364378
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)