changes the color of skipped functional tests (currently grey and can be hard to read/invisible on dark backgrounds) to yellow.
resolves #24791
changes the color of skipped functional tests (currently grey and can be hard to read/invisible on dark backgrounds) to yellow.
resolves #24791
Thanks Jacob for picking this up!
Reviewers should also read #24791. As mentioned there, we want to avoid having PRs changing the color every other month. Maybe removing the coloring of the skipped tests altogether is a alternative if this is too controversial or there are users for which this doesn't work.
For me, this change makes the output visible and readable.
<details> <summary> before and after screenshots on my system </summary>
before:

with this PR:

</details>
look at the pretty colors !!!

No, I was skeptical but have to admit this is better. It's a similar argument as with code comments, you don't want an editor style that hides them. Black/grey is always a subdued color (at least on a dark-ish background). ACK 230e945cd029640a465b7c12371d732c18d6628d
Concept ACK
And warm welcome as a new contributor! 🎉
Changes the color of skipped functional tests to the default text color of the terminal. This will make skipped tests easy to read on the majority of background colors rather than the original grey color (hard to read on dark backgrounds) and the proposed yellow change (hard to read on white backgrounds)
As discussed in #24791 I pushed and squashed some new changes to use the default text color for skipped tests instead. The original color of grey was hard to view on dark backgrounds and the proposed change to yellow would be hard to view on light backgrounds but the default color should support most use cases.
With my terminal settings, before:
After:

Personally prefer old one, but, OTOH, NBD.
Results on my terminal: <img width="635" alt="Screen Shot 2022-04-07 at 14 26 45" src="https://user-images.githubusercontent.com/19480819/162261813-4b05e08e-28fe-4034-9675-119c4c59a68e.png">
I think the white color stands out more than the others ones, I prefer the old one because that 'color' doesn't stand out so much compared to the other colors (which is good since these tests were skipped).
Before:

After:

With the new colour scheme the skipped tests stand out more than the passed ones on my terminal so I prefer the old settings, but NBD.
58 | @@ -59,10 +59,10 @@ 59 | kernel32.SetConsoleMode(stderr, stderr_mode.value | ENABLE_VIRTUAL_TERMINAL_PROCESSING) 60 | # primitive formatting on supported 61 | # terminal via ANSI escape sequences: 62 | + DEFAULT = ('\033[0m', '\033[0m') 63 | BOLD = ('\033[0m', '\033[1m') 64 | GREEN = ('\033[0m', '\033[0;32m') 65 | RED = ('\033[0m', '\033[0;31m') 66 | - GREY = ('\033[0m', '\033[1;30m')
Merging this because it's an improvement in at least this regard.
I'm also fine with using the default color. That said, this is becoming a bikeshed-fest just as I expected.
Tested ACK 3258bad996262792ba77573d6080dafa3952929c
Personally I never had problems as on my terminal the original grey color is clearly visible, but considering that for some it isn't (as seen in some of the screenshots posted) I think it makes sense to change to default color.
Tested ACK https://github.com/bitcoin/bitcoin/commit/3258bad996262792ba77573d6080dafa3952929c
To me, this is an improvement. Thanks for working on this, and welcome as a new contributor :)