Lower yum log level to avoid travis log length limit on centos-6 #199
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Got this error when beginning the second suite of tests > The job exceeded the maximum log length, and has been terminated. Other platforms do not have as many progress bars. Compare these build logs to see why the YUM Progress bars are so problematic. without this change: https://api.travis-ci.org/v3/job/430822100/log.txt with this change: https://api.travis-ci.org/v3/job/431074530/log.txt Look below the line that includes: > Retrieving https://dl.fedoraproject.org/pub/epel You will see pages and pages of useless epel/other download progress bars.
|
Extracted from #162 as it is helpful independent of that PR. |
arm4b
approved these changes
Sep 21, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an optimization for tests that run on Travis.
Got this error when beginning the second suite of tests
Other platforms do not have as many progress bars.
Compare these build logs to see why the YUM Progress bars are so
problematic.
without this change:
https://api.travis-ci.org/v3/job/430822100/log.txt
with this change:
https://api.travis-ci.org/v3/job/431074530/log.txt
Look below the line that includes:
You will see pages and pages of useless epel/other download progress bars.