Re: [Pgbuildfarm-members] pgsql-Git-Dirty failures on jaguarundi

* Stefan Kaltenbrunner wrote:

> On 05/15/2013 10:39 AM, Christian Ullrich wrote:

>> for a few weeks, jaguarundi has been failing frequently at a stage
>> called "pgsql-Git-Dirty". As far as I can tell, that means that git has
>> printed an unexpected message, in this case, that it took a long time
>> (several seconds) to perform "git status".

> any chance you have upgraded your git binaries recently? Git changed the
> output format a while ago and you need a very recent version of the
> buildfarm client script to support that.

Git is 1.8.2.1, buildfarm is fbebb3925b (=HEAD).

SCM.pm produces this error if the status output contains anything that
does not match "/Already.up-to-date|On branch bf_$branch|nothing to
commit\W+working directory clean/". In jaguarundi's case, I get

# It took 3.18 seconds to enumerate untracked files. 'status -uno'
# may speed it up, but you have to be careful not to forget to add
# new files yourself (see 'git help status').

plus whatever was filtered out because it matched the regex above.

--
Christian