Re: [PATCH 2/2] Fix t3404 assumption that `wc -l` does not use whitespace.

From: Mike Ralphson <mike.ralphson@gmail.com>
Date: May 13, 2008, 18:10 UTC
Message-ID: <e2b179460805131110k3cf582fdn9b8bd31046b90ca7@mail.gmail.com>
In-Reply-To: <20080513091143.GA26248@sigill.intra.peff.net>

2008/5/13 Jeff King <peff@peff.net>:

Show 17 quoted lines

>
> 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