[
https://issues.apache.org/jira/browse/DRILL-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488334#comment-16488334
]
ASF GitHub Bot commented on DRILL-6437:
---------------------------------------
priteshm commented on issue #1285: DRILL-6437: Removed excess maven logging
when downloading dependencies. This fixed Travis failures due to log overflow.
URL: https://github.com/apache/drill/pull/1285#issuecomment-391571029
@parthchandra or @arina-ielchiieva can you please review this change?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
> Fix For: 1.14.0
>
>
> 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)
