From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Sverre Rabbelier" <srabbelier@gmail.com>
Cc: git@vger.kernel.org, dsymonds@gmail.com
Subject: Re: [PATCH 3/3] Hook up the result aggregation in the test makefile.
Date: Mon, 12 May 2008 17:03:29 +0200 [thread overview]
Message-ID: <19f34abd0805120803h6a976d1fvcc49a43c192fe517@mail.gmail.com> (raw)
In-Reply-To: <1210584832-16402-4-git-send-email-srabbelier@gmail.com>
Hi,
On Mon, May 12, 2008 at 11:33 AM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> This patch makes 'make' output the aggregated results at the end of each build.
> The 'git-test-result' file is removed both before and after each build.
>
> Signed-off-by: Sverre Rabbelier <srabbelier@gmail.com>
> ---
> t/Makefile | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/t/Makefile b/t/Makefile
> index 72d7884..3955ee8 100644
> --- a/t/Makefile
> +++ b/t/Makefile
> @@ -14,13 +14,20 @@ SHELL_PATH_SQ = $(subst ','\'',$(SHELL_PATH))
> T = $(wildcard t[0-9][0-9][0-9][0-9]-*.sh)
> TSVN = $(wildcard t91[0-9][0-9]-*.sh)
>
> -all: $(T) clean
> +all: pre-clean $(T) aggregate-results clean
>
> $(T):
> @echo "*** $@ ***"; GIT_CONFIG=.git/config '$(SHELL_PATH_SQ)' $@ $(GIT_TEST_OPTS)
>
> +pre-clean:
> + $(RM) -f /tmp/git-test-results
> +
> clean:
> $(RM) -r trash
> + $(RM) -f /tmp/git-test-results
> +
> +aggregate-results:
> + ./key_value_parser.py
>
> # we can test NO_OPTIMIZE_COMMITS independently of LC_ALL
> full-svn-test:
> --
> 1.5.5.1.178.g1f811
I am not really familiar with the git makefile in particular, but
usually it's a good idea to put
.PHONY: pre-clean aggregate-results
as well if these targets are not output files. (Rationale can be found
in section 4.6 "Phony Targets" of the GNU make manual.)
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-05-12 15:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 9:33 [PATCH 0/3] Aggregate testcase results Sverre Rabbelier
2008-05-12 9:33 ` [PATCH 1/3] Modified test-lib.sh to output stats to /tmp/git-test-results Sverre Rabbelier
2008-05-12 14:55 ` Vegard Nossum
2008-05-12 9:33 ` [PATCH 2/3] A simple python script to parse the results from the testcases Sverre Rabbelier
2008-05-12 10:14 ` Jakub Narebski
2008-05-12 10:16 ` Sverre Rabbelier
2008-05-12 13:00 ` Johannes Schindelin
2008-05-12 13:05 ` Sverre Rabbelier
2008-05-12 13:24 ` Johannes Schindelin
2008-06-08 0:18 ` [PATCH] A simple " Miklos Vajna
2008-06-08 0:34 ` Sverre Rabbelier
2008-06-08 0:49 ` Miklos Vajna
2008-06-08 0:56 ` Sverre Rabbelier
2008-06-08 2:26 ` Miklos Vajna
2008-06-08 11:43 ` Sverre Rabbelier
2008-06-08 17:27 ` Johannes Schindelin
2008-06-08 17:30 ` Sverre Rabbelier
2008-06-08 18:06 ` Mikael Magnusson
2008-06-08 18:09 ` Sverre Rabbelier
2008-05-12 9:33 ` [PATCH 3/3] Hook up the result aggregation in the test makefile Sverre Rabbelier
2008-05-12 15:03 ` Vegard Nossum [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-08 14:04 [PATCH 1/3] Modified test-lib.sh to output stats to /tmp/git-test-results Sverre Rabbelier
2008-06-08 14:04 ` [PATCH 3/3] Hook up the result aggregation in the test makefile Sverre Rabbelier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19f34abd0805120803h6a976d1fvcc49a43c192fe517@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).