Skip colors on travis job#1034
Conversation
They disabled logs when nb_lines > 10000, which is our case, this helps debugging
|
Thanks @soyuka |
|
Probably a better fix would be to reduce the verbosity of some of the installation logs. Colours are good... |
|
Behat alone is >10k lines no? |
|
Okay, now I'm not sure I get what this PR is supposed to do... \o/ |
|
I don't remember what PR it was but the author was asking for help debugging. I had to fork his branch to execute the tests on my device because travis output was unreadable because colors where stripped. Can't find the reference, but travis clearly stated that above 10 000 lines, colors won't be outputted and we'll instead get ASCII characters. |
|
I think Travis stops showing log output when it hits 10000 lines (it's still available in the raw log). The way mozilla/fxa-content-server#488 handled it (reducing verbosity where unneeded) seems better to me. |
|
Damn, I need to get my hand on the screenshot again. Anyway, if you really want colors back we can revert this ^^ but it's not a priority imo. |
|
No colours = hard to read. Symfony uses colours too... 😛 https://github.com/symfony/symfony/blob/59f3f34cc84e93e287e0971d05bfe0edee8e20e2/.travis.yml |
Many unix users would actually tell you that it is more a distraction 😛 . Thing is, it's way more readable than when colors are ASCII outputed no? |
Skip colors on travis job
3 participants
They disabled logs when nb_lines > 10000, which is our case, this helps
debugging