David Frech, Fri, Jul 13, 2007 02:33:19 +0200:
> On 7/12/07, David Frech <nimblemachines@xxxxxxxxx> wrote:
> >On 7/12/07, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> >> Then a nightly update would go like this:
> >>
> >> $ cd ~/nightly-git
> >> $ git pull origin next
> >> $ make clean
> >> $ make test || barf
>
> One more thing: would it make sense to do "make -k test" so that *all*
> failures (if >1) show up?
Yes, definitely. You'll find you will see failures which you know are
already fixed, just didn't reach the nightly-build yet.
BTW, do _not_ send the errors to this mailing list. It just too easy
gets out of control. And consider saving the build log somewhere after
doing a _completely_ clean build, i.e. like this:
#!/bin/bash
cd ~/nightly-git || exit
echo 'Subject: Nightly build git next ' $(date) >/tmp/mail.msg
echo >>/tmp/mail.msg
{
rm -rf * # it does not remove .git
git reset --hard
git pull origin next || exit 1
make || exit 1
make -k test|| exit 1
} &>> /tmp/mail.msg
$ nightly-build || sendmail local-user@localhost < /tmp/mail.msg
It is simplier to find out what went wrong if you know what state did
you have before doing the test. And the state after rm -rf * is very
simple to predict.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
