NO_COLOR=1 does not suppress all color escapes

Current behavior:

As mentioned here https://github.com/cypress-io/cypress/issues/1748#issuecomment-390682159 there is a NO_COLOR=1 flag. (It doesn’t seem documented though, I found it via Google. Maybe that’s another issue though.)

When this is set, most of the colors are suppressed, but I still see some things in the CI logs that seem like color escape codes.

2019-10-29T10:49:45.5683027Z     ✓ should allow brand creation (11492ms)
2019-10-29T10:49:51.2829146Z     ✓ should not allow creating the same brand (5803ms)
2019-10-29T10:49:51.3044692Z 
2019-10-29T10:49:51.3056465Z 
2019-10-29T10:49:51.3057924Z   2 passing (17s)`

Desired behavior:

There should be no escape codes in the output, just ascii chars.

Steps to reproduce: (app code and test code)

1. Set up a CI build on Azure Devops.
2. Run Cypress with NO_COLOR=1 env var via Docker with the following command:

docker run --rm -t -e NO_COLOR=1 -v /work/agent-0/r1/a/src/cypress-files:/src cypress/included:3.4.1 -P /src

Versions

Cypress 3.4.1 running via Docker:

docker run --rm -t -e NO_COLOR=1 -v /work/agent-0/r1/a/src/cypress-files:/src cypress/included:3.4.1 -P /src

[punkrockbuddyholly]

Not sure if this will help anyone but I’m running a Cypress docker image in a jenkinsfile and I found that I had to pass the NO_COLOR=1 env var to the docker run part rather than as an env flag passed to cypress run. Previously I was running cypress run --env NO_COLOR=1 and it was making no difference.

[pitgrap]

Another Information to this topic:

We have problems with our Cypress runs stdout in Jenkins. So we added “NO_COLOR=1”, but the problem didn’t disappear. I just retestet it locally on my machine and found colors in the summary.

tl;dr All outputs are free of color except the summary. See screenshot Is this a known issue? Shall I open a new issue?