If it works - should reduce running time (IMHO, we had similar issues with unit tests, in
the past)
2. Shouldn't reducing the number of processes improve the situation?
----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
Cc: "Michal Skrivanek" <michal.skrivanek(a)redhat.com>, infra(a)ovirt.org
Sent: Friday, May 31, 2013 6:44:58 PM
Subject: Re: gerrit is down
On 05/31/2013 06:37 PM, Yair Zaslavsky wrote:
>
> ----- Original Message -----
>> From: "Itamar Heim" <iheim(a)redhat.com>
>> To: "Michal Skrivanek" <michal.skrivanek(a)redhat.com>
>> Cc: infra(a)ovirt.org
>> Sent: Friday, May 31, 2013 12:07:38 PM
>> Subject: Re: gerrit is down
>>
>> On 05/31/2013 11:31 AM, Michal Skrivanek wrote:
>>> anyone can fix it?
>>>
>>> Thansk,
>>> michal
>>> _______________________________________________
>>> Infra mailing list
>>> Infra(a)ovirt.org
>>>
http://lists.ovirt.org/mailman/listinfo/infra
>>>
>>
>> up again.
>> it was very loaded - i suspect the new findbugs job per gerrit patch.
>> i ran a git compact which should improve things.
>> if not, we'll need to disable the findbugs job again (sadly).
>
> Hi Itamar,
> During my latest work on findbugs, I saw that we run with fork = true.
> Worth considering to run with fork = false.
how would fork affect the git on gerrit?
>
> Yair
>
>
>> _______________________________________________
>> Infra mailing list
>> Infra(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/infra
>>