| From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
|---|---|
| To: | Christian Ullrich <chris(at)chrullrich(dot)net> |
| Cc: | pgbuildfarm-members(at)pgfoundry(dot)org |
| Subject: | Re: [Pgbuildfarm-members] pgsql-Git-Dirty failures on jaguarundi |
| Date: | 2013-05-15 09:12:49 |
| Message-ID: | 51935191.8030103@kaltenbrunner.cc |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-members |
On 05/15/2013 10:39 AM, Christian Ullrich wrote:
> Hello all,
>
> 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".
>
> This started at about the same time the machine lost one of its mirrored
> hard drives. The drive was replaced quickly, but the buildfarm errors
> did not stop.
>
> I have tried to "git gc" the local repository, with no effect. When I
> run "git status" by hand in the branch checkouts, it always finishes
> within milliseconds.
>
> What can I do to fix this?
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.
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Ullrich | 2013-05-15 09:50:56 | Re: [Pgbuildfarm-members] pgsql-Git-Dirty failures on jaguarundi |
| Previous Message | Christian Ullrich | 2013-05-15 08:39:46 | [Pgbuildfarm-members] pgsql-Git-Dirty failures on jaguarundi |