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

From: Jeff King <peff@peff.net>
Date: May 13, 2008, 09:11 UTC
Message-ID: <20080513091143.GA26248@sigill.intra.peff.net>
In-Reply-To: <e2b179460804280256g4ff903bu39c9460086df7157@mail.gmail.com>

On Mon, Apr 28, 2008 at 10:56:05AM +0100, Mike Ralphson wrote:

Show 9 quoted lines

> > If a failing test, then I wonder if we could get a few people to set up
> > automated tests on alternate platforms. IIRC, Junio makes sure that
> > master always passes test on his Linux box and KO (Debian and Redhat, I
> > think?). Other platforms could "git pull && make test" daily. I could
> > probably do Solaris (once I get the tests to complete pass at all!) and
> > FreeBSD 6.
> 
> 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.

-- >8 -- #!/bin/sh

dir=$1; shift log="$dir/.autotest.out"

try() {
  "$@" >"$log" 2>&1
  case "$?" in
    0) ;;
    *) echo >&2 "autotest failed: $*"
       cat >&2 "$log"
       exit 1
       ;;
  esac
}

try cd "$dir" try git pull try gmake PATH=/usr/local/bin:/usr/bin:/bin; export PATH try gmake test