Travis: avoid exceeding log length limit #21
Conversation
|
Well that didn't work. Back to the drawing board, then. Sorry about the noise. |
Recent Cargo versions started printing out a progress bar, which has to be re-painted every time something is outputted. Since we're using `-vv`, the progress bar effectively doubles the amount of output. We now suppress the progress bar in all builds.
|
My previous attempt failed because the I'll merge this once the build finishes. |
|
[The build finished successfully[(https://travis-ci.org/github/Koka/gettext-rs/builds/723892058), but GitHub doesn't show that for whatever reason :( Merging this still. |
|
Ah wait, I can't merge because because the status is required for merging. @Koka, can you merge this please? |
|
@Minoru done! |
|
Thanks! I notice there are no Travis statuses on recent commits to master either, researching that now. |
|
Thanks, I'll try a bit later |
|
Tried with no luck, apparently github integration with older travis-ci.org is broken, I'll try to migrate to newer travis-ci.com |
|
Apparently it works properly now |
|
Still doesn't work for PRs submitted from my fork (the "branch" check is never reported), but I can push directly to this repo and it works then, so it's not a big deal. Thanks for fixing it! |
Two Travis jobs currently fail because their output exceeds log length limit:
By
diffing 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
TERMenvironment variable todumbto disable the progress bar. I believe this won't affect the usefulness of the output.