From: Sverre Rabbelier <srabbelier@gmail.com>
To: git@vger.kernel.org
Cc: dsymonds@gmail.com
Subject: [PATCH 0/3] Aggregate testcase results
Date: Mon, 12 May 2008 11:33:49 +0200 [thread overview]
Message-ID: <1210584832-16402-1-git-send-email-srabbelier@gmail.com> (raw)
Heya,
The following patch series provides a summary of the test results at
the end of each 'full run'. The reason I wrote this series is that I
noticed when running 'make' in '/t/' that there is no way for me to
find out if all testcases still pass without scrolling through the
output. Since almost all testcases -do- pass anyway, and it takes
quite a long time to run them all I wanted a way to see at a glance if
a change I made breaks something (that is covered by the testcases).
Cheers,
Sverre Rabbelier
next reply other threads:[~2008-05-12 10:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 9:33 Sverre Rabbelier [this message]
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
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=1210584832-16402-1-git-send-email-srabbelier@gmail.com \
--to=srabbelier@gmail.com \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
/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).