You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's the raw outputs of a different repo I have running mocha+travis:
Not truncated, colorized (using mocha) output from travis:
[0m [0m
[0m CAR COLOR: [0m
[0m find [0m
[2K [0G [32m ✓ [0m [90m return all car colors [0m [33m (55ms) [0m
[2K [0G [32m ✓ [0m [90m return all managed car colors [0m
[2K [0G [32m ✓ [0m [90m return all unmanaged car colors [0m
Truncated, colorized turned off (using mocha --no-colors) output from travis:
CAR COLOR:
find
[2K [0G ✓ return all car colors (48ms)
[2K [0G ✓ return all managed car colors
[2K [0G ✓ return all unmanaged car colors
I've spoken with Travis and they have a couple issues already open for it. Support Engineer's reply:
I am afraid that some escape sequences are hard to emulate on line-oriented log display like ours. For example, [nK (https://github.com/travis-ci/travis-ci/issues/1950) and [nG (https://github.com/travis-ci/travis-ci/issues/1951) are not supported as a result.
Is there a way to suppress these ANSI sequences on your testing tool?
The text was updated successfully, but these errors were encountered:
kevinawoo
changed the title
Travis --no-color
Travis --no-color, truncated test cases
Jan 20, 2016
I am a bot that watches issues for inactivity.
This issue hasn't had any recent activity, and I'm labeling it stale. In 14 days, if there are no further comments or activity, I will close this issue.
Thanks for contributing to Mocha!
When testing using Travis using the option
--no-colors
, color escape codes are still being outputted. This leads to some test cases being truncated.Latest mocha master branch
See Travis with --no-color option
Here's the raw outputs of a different repo I have running mocha+travis:
Not truncated, colorized (using mocha) output from travis:
Truncated, colorized turned off (using mocha --no-colors) output from travis:
I've spoken with Travis and they have a couple issues already open for it. Support Engineer's reply:
The text was updated successfully, but these errors were encountered: