Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
1.14.0
-
None
Description
The Travis logs are flooded when downloading mysql.
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
And the Travis build fails with
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
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
Attachments
Issue Links
- links to