git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v6 0/7] make test output coloring more intuitive

From
Jeff King <peff@peff.net>
Date
Dec 20, 2012, 16:11 UTC
Message-ID
<20121220161110.GA10605@sigill.intra.peff.net>
In-Reply-To
<CAOkDyE9y6JvNKTCBoJqu47Hn-3axfjZPUdBhf4bOEfSP-9Q84A@mail.gmail.com>
On Thu, Dec 20, 2012 at 03:44:53PM +0000, Adam Spiers wrote:
Show 18 quoted lines
> > diff --git a/t/test-lib.sh b/t/test-lib.sh
> > index 256f1c6..31f59af 100644
> > --- a/t/test-lib.sh
> > +++ b/t/test-lib.sh
> > @@ -227,7 +227,7 @@ then
> >                 pass)
> >                         tput setaf 2;;            # green
> >                 info)
> > -                       tput bold; tput setaf 6;; # bold cyan
> > +                       tput setaf 6;; # cyan
> >                 *)
> >                         test -n "$quiet" && return;;
> >                 esac
> >
> 
> Good point, I forgot to check what it looked like with -v.  Since this
> series is already on v6, is there a more lightweight way of addressing
> this tiny tweak than sending v7?

It is ultimately up to Junio, but I suspect he would be OK if you just reposted patch 4/7 with the above squashed. Or even just said "I like this, please squash it into patch 4 (change info messages from yellow/brown to bold cyan).

As an aside, it made me wonder how hard/useful it would be to color the snippets even more. Doing this:

diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index f9ccbf2..3d44a94 100644
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -364,7 +364,12 @@ test_expect_success () {
 	export test_prereq
 	if ! test_skip "$@"
 	then
-		say >&3 "expecting success: $2"
+		if test -z "$GIT_TEST_HIGHLIGHT"; then
+			say >&3 "expecting success: $2"
+		else
+			say >&3 "expecting success:"
+			echo "$2" | eval "$GIT_TEST_HIGHLIGHT"
+		fi
 		if test_run_ "$2"
 		then
 			test_ok_ "$1"

produces highlighted snippets with:

  GIT_TEST_HIGHLIGHT='highlight -S sh -O ansi'

or

  GIT_TEST_HIGHLIGHT='pygmentize -l sh'

depending on what you have installed on your system. I'm not convinced
it actually adds anything, but it's a fun toy. A real patch would
probably turn it off in non-verbose mode, as invoking the highlighter
(especially pygmentize) repeatedly is somewhat expensive.

-Peff
Previous: Adam SpiersNext: Adam Spiers
Message 14 of 18 in “make test output coloring more intuitive”
  1. 0/7 make test output coloring more intuitiveAdam Spiers, Dec 16, 2012
  2. 1/7 tests: test number comes first in 'not ok $count - $message'Adam Spiers, Dec 16, 2012
  3. 2/7 tests: paint known breakages in bold yellowAdam Spiers, Dec 16, 2012
  4. 3/7 tests: paint skipped tests in bold blueAdam Spiers, Dec 16, 2012
  5. 4/7 tests: change info messages from yellow/brown to bold cyanAdam Spiers, Dec 16, 2012
  6. 5/7 tests: refactor mechanics of testing in a sub test-libAdam Spiers, Dec 16, 2012
  7. 6/7 tests: test the test framework more thoroughlyAdam Spiers, Dec 16, 2012
  8. 7/7 tests: paint unexpectedly fixed known breakages in bold redAdam Spiers, Dec 16, 2012
  9. Junio C HamanoDec 16, 2012
  10. Adam SpiersDec 16, 2012
  11. Junio C HamanoDec 16, 2012
  12. Jeff KingDec 20, 2012
  13. Adam SpiersDec 20, 2012
  14. Jeff KingDec 20, 2012
  15. Adam SpiersDec 20, 2012
  16. Junio C HamanoDec 20, 2012
  17. Jeff KingDec 20, 2012
  18. Adam SpiersDec 20, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.