From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Thu, 12 Aug 2010 16:50:32 GMT
Subject: Re: What's cooking in git.git (Aug 2010, #02; Wed, 11)
Message-ID: <AANLkTina+62MczLNhXC6VCtz_kQZ_t0+uZ8fH=vTV=XO@mail.gmail.com>
In-Reply-To: <AANLkTi=N-fA9r-Akm3_=ucFYew8BhcsQoWM-Z9S8+58C@mail.gmail.com>

On Thu, Aug 12, 2010 at 11:35, Erik Faye-Lund <kusmabite@gmail.com> wrote:
> On Thu, Aug 12, 2010 at 12:20 PM, Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>> On Thu, Aug 12, 2010 at 09:23, Johannes Sixt <j.sixt@viscovery.net> wrote:
>>> [Sorry for the Cc spam; I lack the time to conduct individual messages.]
>>>
>>> I compiled many topics in pu and ran the test suite on Windows,
>>
>> A Windows smoker would be useful :)
>>
>
> I guess I could look into setting one up. Where would I look for the
> most up-to-date instructions on doing this?

The smoke testing section in t/README in pu.

Here's a small script I use to automate my smoke reports:
http://github.com/avar/linode-etc/blob/master/bin/cron/build-and-install-git

But it's crappy and incomplete, we/I still need to write something
easy to set up that does automatic bisecting etc. on errors, tests
multiple branches and all that good stuff.

In the meantime smoking pu daily in cron should do.