Re: [Pgbuildfarm-members] Multiple buildfarm critters showing similar "Git-Dirty" failures

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, jochen(at)pgfarm(dot)erwied(dot)eu, Richard Tector <richard(at)tector(dot)org(dot)uk>
Cc: PGBuildFarm <pgbuildfarm-members(at)pgfoundry(dot)org>
Subject: Re: [Pgbuildfarm-members] Multiple buildfarm critters showing similar "Git-Dirty" failures
Date: 2012-11-05 12:41:51
Message-ID: 5097B40F.3090801@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members


On 11/04/2012 10:23 PM, Tom Lane wrote:
> These log reports don't look like they should be failures at all:
>
> Already up-to-date.
> ===========nothing to commit, working directory clean
>
> Something broken?
>
>

A recent release of git changed the format of its status message subtly.
We fixed one member last week but it looks like these three have updated
their git since then.

The fix is to apply the attached patch, or download a new SCM.pm from
<https://github.com/PGBuildFarm/client-code/raw/master/PGBuild/SCM.pm>

I'll push out a new release in the next day or two.

cheers

andrew

Attachment Content-Type Size
bf-git-patch text/plain 410 bytes

Browse buildfarm-members by date

  From Date Subject
Next Message Andrew Dunstan 2012-11-12 15:40:57 Version 4.9 of PostgreSQL buildfarm client released
Previous Message Andrew Dunstan 2012-09-25 23:22:17 Re: new buildfarm client release 4.8