-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Tests are failing because of color schema changes #345
Comments
Is it okay, if I take a look at this issue? I would appreciate it if you have any pointers on how to approach it. |
@poojankhanpara sure. The problem is conversion between cheat text into ANSI sequences. As you see, in |
Thanks! I tried using both ;246; and ;248; and it turns out it changes the color of the comments to a bit brighter shade of gray. Where is the color added to the comments? Maybe there is no need to turn off upstream tests for docker if we can get the same colored comment on docker too. |
Thinking of adding an option to remove ansi styling with the help of ?T option in run_tests.sh. And carefully recapture the output. |
The change from $ CHEATSH_UPDATE_TESTS_RESULTS=YES bash tests/run-tests.sh will update the results files ( Note that there were recent updates to |
I tried to run a local server with legacy pygments and colored module and I am still getting the same color change difference. Somehow tests on live production are passing. I have a feeling that recapturing the output might hide the real problem. |
Tests are failing, because ANSI markup is different. This is a server bug, but need to check it is only for https://cht.sh or if it is repeated with local server in Docker container. Need to turn off upstream query for Docker tests.
The text was updated successfully, but these errors were encountered: