Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect formatting inside Travis CI?? #90

Open
jlmakes opened this issue Feb 1, 2017 · 5 comments
Open

Incorrect formatting inside Travis CI?? #90

jlmakes opened this issue Feb 1, 2017 · 5 comments
Assignees

Comments

@jlmakes
Copy link

jlmakes commented Feb 1, 2017

screen shot 2017-02-01 at 4 44 19 am

There's an extra indentation after an odd [32m, and some text that doesn't render green.

I'm using version ^2.2.0 of the reporter, and and Karma ^1.3.0, so everything should be running the latest releases. Is there more information I can provide to help identify what the issue is?

@4kochi
Copy link
Collaborator

4kochi commented Feb 1, 2017

Can you share the link to the travis build?

@4kochi 4kochi self-assigned this Feb 1, 2017
@jlmakes
Copy link
Author

jlmakes commented Feb 1, 2017

Sure!

https://travis-ci.org/jlmakes/scrollreveal/builds/197391631

Also I'm not sure if relevant, but I'm using sauce labs (and the karma-sauce-launcher) to test in various browser environments. I'm going to experiment using only PhantomJS to see if the output looks different.

@4kochi
Copy link
Collaborator

4kochi commented Feb 1, 2017

The code [32m is part of the ansi color code of the green color ('\u001B[32m'). It is generated by the color module we use in this reporter (chalk).

It works fine on my machine. Don't know what the issue with travis could. Generally no colors are printed if a shell does not support the ansi color codes. Normally it works fine in travis.

@jlmakes
Copy link
Author

jlmakes commented Feb 2, 2017

Yeah, the reporter works great on my local machine as well.

. . .

Well perhaps I'll move over to Circle CI...😨 the mere thought of the odd developer perusing through my tests and seeing malformed reporting—what tremendous embarrassment! I'd be the laughing stock of the town! 😤

. . .

Any ideas on debugging?

@4kochi
Copy link
Collaborator

4kochi commented Feb 2, 2017

This will be hard to debug. But trying another CI System might help to find out if it is just an problem in travis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants