-
Notifications
You must be signed in to change notification settings - Fork 214
[bz5964521] test output is always colorized -- includes escape codes when saved to file #809
Comments
yes, test.js implements different console text coloring functions that are not tty aware. I have a branch or stash somewhere I think that started converting the code to use utils.js style tty aware colors... |
@jlecomte is reporting this is still occurring with 0.5.1 |
pull #872 prevents color codes being output in test results, when piped to a file (or other non-tty usage). However, output from other mojito components still send colorized output (lib/app/autoload/perf.server.js, and some Y.log calls). Closing this, and will track the various other offenders separately. |
Runtime logs are now processed correctly (since 0.5.2). Test, cli and store logs are still having issues with encoding. |
@caridy test & cli logging are tty aware. escape codes are coming from code-under-test and elsewhere, right? |
as mentioned there are some color codes output when running
|
When running tests, the output is colorized always.
E.g. the build output includes color escape codes. See BZ ticket for link.
@isao says there are two code paths for output -- he's fixed the console path to check whether output is a TTY and skip colors. However the test path is still colorizing everything by default.
Example
The text was updated successfully, but these errors were encountered: