Travis: avoid exceeding log length limit #21
Merged
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.
Two Travis jobs currently fail because their output exceeds log length limit:
By
diff
ing the output with the last passing job, https://travis-ci.org/github/Koka/gettext-rs/jobs/417123508, I found that Cargo now prints out a progress bar. Travis stores each update of the progress bar as a separate line in the log, which eventually reaches the limit.This is a known problem (rust-lang/cargo#5721), and I applied the suggested solution, which is: set
TERM
environment variable todumb
to disable the progress bar. I believe this won't affect the usefulness of the output.