git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Mike Ralphson <mike.ralphson@gmail.com>
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 05:11:43 -0400	[thread overview]
Message-ID: <20080513091143.GA26248@sigill.intra.peff.net> (raw)
In-Reply-To: <e2b179460804280256g4ff903bu39c9460086df7157@mail.gmail.com>

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

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

  reply	other threads:[~2008-05-13  9:12 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 [this message]
2008-05-13 18:10           ` Mike Ralphson
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=20080513091143.GA26248@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=benji@silverinsanity.com \
    --cc=git@vger.kernel.org \
    --cc=mike.ralphson@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).