-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
assert
colors don’t match test
colors
#52249
Comments
This could be a duplicate of #50397, but I have not confirmed it. |
@pmarchini was this issue fixed by your work in #55404? |
@cjihrig it should be addressed. |
Looking at #55404, it looks like that change was released in v23.1.0 and has not been backported to the v22 release line. |
IMO a backport would be nice, but definitely not critical. I look forward to seeing this change in a near future. Thanks for fixing this! ❤️ |
Version
v20.12.0
Platform
Linux vali 6.8.0-76060800daily20240311-generic #202403110203
171019808822.04~1a3dbc7 SMP PREEMPT_DYNAMIC Mon M x86_64 x86_64 x86_64 GNU/LinuxSubsystem
assert
What steps will reproduce the bug?
Create an empty directory with the following file named
test.mjs
:Now run the following:
How often does it reproduce? Is there a required condition?
In my experience always.
What is the expected behavior? Why is that the expected behavior?
I expected the assertion error to always be colorful, at least if the rest of the test output is.
What do you see instead?
The assertion error is colorful when running a test script directly, but not when it’s run via
node --test
.Additional information
Potentially related environment variables from my desktop session:
From a Docker container:
The text was updated successfully, but these errors were encountered: