From: "Mike Ralphson" <mike.ralphson@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Brian Gernhardt" <benji@silverinsanity.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [PATCH 2/2] Fix t3404 assumption that `wc -l` does not use whitespace.
Date: Tue, 13 May 2008 19:10:30 +0100 [thread overview]
Message-ID: <e2b179460805131110k3cf582fdn9b8bd31046b90ca7@mail.gmail.com> (raw)
In-Reply-To: <20080513091143.GA26248@sigill.intra.peff.net>
2008/5/13 Jeff King <peff@peff.net>:
>
> On Mon, Apr 28, 2008 at 10:56:05AM +0100, Mike Ralphson wrote:
> > I could run automated build / test [/ bisect?] cycles on AIX if of any
> > interest.
>
> I think that would be helpful. We seem to have most Linux variants
> pretty well covered. I now have a daily pull/build/test running on a
> FreeBSD 6.1 box. I am going to try to get a Solaris one going, too, but
> I have to first actually get the test scripts to pass _once_. :)
>
> AIX would be nice, since it seems easy to break. ;) OS X would be nice,
> too, though I suspect there are a few developers (Shawn?) who end up
> running the test scripts occasionally anyway.
>
> I am just calling the script below through cron, and it dumps a bunch of
> output if any test fails (at which point I go investigate manually). The
> only argument is the path to a git repo.
Thanks - that was a helpful spur to action. I'll check tomorrow how it
fairs pulling, building, running the tests etc. I've added a couple of
'try git tag -f's to it, so I have KNOWN_BUILDING and KNOWN_PASSING
points to pass quickly into bisect if necessary.
I'll shout the first time something breaks (after doing a bit of
rudimentary investigation), then maybe we can look at a way of
aggregating the build/test statuses and whether that should be pushed
to a website (or git repo, obviously) or some kind of alert.
Cheers, Mike
next prev parent reply other threads:[~2008-05-13 18:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 15:16 [PATCH 2/2] Fix t3404 assumption that `wc -l` does not use whitespace Brian Gernhardt
2008-04-27 15:22 ` Johannes Schindelin
2008-04-27 15:32 ` Brian Gernhardt
2008-04-28 9:41 ` Jeff King
2008-04-28 9:56 ` Mike Ralphson
2008-05-13 9:11 ` Jeff King
2008-05-13 18:10 ` Mike Ralphson [this message]
2008-05-15 10:16 ` Mike Ralphson
2008-05-15 11:20 ` Jeff King
2008-05-15 11:23 ` Jeff King
2008-05-15 17:18 ` Junio C Hamano
2008-05-16 14:22 ` Mike Ralphson
2008-04-28 12:40 ` Brian Gernhardt
2008-04-27 17:31 ` Junio C Hamano
2008-04-28 10:13 ` Johannes Schindelin
2008-04-28 11:40 ` Jörg Sommer
2008-04-28 13:42 ` Johannes Schindelin
2008-04-28 16:30 ` Jörg Sommer
2008-04-28 18:07 ` Johannes Schindelin
2008-04-28 16:19 ` Junio C Hamano
2008-04-28 18:01 ` Johannes Schindelin
2008-04-28 21:24 ` Junio C Hamano
2008-04-28 21:30 ` Johannes Schindelin
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=e2b179460805131110k3cf582fdn9b8bd31046b90ca7@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).