Skip to content

Commit e8e5195

Browse files
aspiersgitster
authored andcommitted
tests: paint known breakages in yellow
Yellow seems a more appropriate color than bold green when considering the universal traffic lights coloring scheme, where green conveys the impression that everything's OK, and amber that something's not quite right. Likewise, change the color of the summarized total number of known breakages from bold red to the same yellow to be less alarmist and more consistent with the above. An earlier version of this patch used bold yellow but because these are all long-known failures, reminding them to developers in bold over and over does not help encouraging them to take a look at them very much. This iteration paints them in plain yellow instead to make them less distracting. Signed-off-by: Adam Spiers <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 5e5c006 commit e8e5195

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

t/test-lib.sh

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -183,6 +183,8 @@ then
183183
tput bold; tput setaf 1;; # bold red
184184
skip)
185185
tput bold; tput setaf 2;; # bold green
186+
warn)
187+
tput setaf 3;; # brown/yellow
186188
pass)
187189
tput setaf 2;; # green
188190
info)
@@ -281,7 +283,7 @@ test_known_broken_ok_ () {
281283

282284
test_known_broken_failure_ () {
283285
test_broken=$(($test_broken+1))
284-
say_color skip "not ok $test_count - $@ # TODO known breakage"
286+
say_color warn "not ok $test_count - $@ # TODO known breakage"
285287
}
286288

287289
test_debug () {
@@ -375,7 +377,7 @@ test_done () {
375377
fi
376378
if test "$test_broken" != 0
377379
then
378-
say_color error "# still have $test_broken known breakage(s)"
380+
say_color warn "# still have $test_broken known breakage(s)"
379381
msg="remaining $(($test_count-$test_broken)) test(s)"
380382
else
381383
msg="$test_count test(s)"

0 commit comments

Comments
 (0)