This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC Buildbot Update - Definition of regression
- From: Paulo Matos <pmatos@linki.tools>
- To: gcc at gcc dot gnu dot org
- Date: Wed, 11 Oct 2017 08:22:07 +0200
- Subject: Re: GCC Buildbot Update - Definition of regression
- Authentication-results: sourceware.org; auth=none
- References: <3b204c53-7613-ffe2-172b-69ad2a781ceb@linki.tools> <20171011041755.GA13028@x4>
On 11/10/17 06:17, Markus Trippelsdorf wrote:
> On 2017.10.10 at 21:45 +0200, Paulo Matos wrote:
>> Hi all,
>>
>> It's almost 3 weeks since I last posted on GCC Buildbot. Here's an update:
>>
>> * 3 x86_64 workers from CF are now installed;
>> * There's one scheduler for trunk doing fresh builds for every Daily bump;
>> * One scheduler doing incremental builds for each active branch;
>> * An IRC bot which is currently silent;
>
> Using -j8 for the bot on a 8/16 (core/thread) machine like gcc67 is not
> acceptable, because it will render it unusable for everybody else.
I was going to correct you on that given what I read in
https://gcc.gnu.org/wiki/CompileFarm#Usage
but it was my mistake. I assumed that for an N-thread machine, I could
use N/2 processes but the guide explicitly says N-core, not N-thread.
Therefore I should be using 4 processes for gcc67 (or 0 given what follows).
I will fix also the number of processes used by the other workers.
> Also gcc67 has a buggy Ryzen CPU that causes random gcc crashes. Not the
> best setup for a regression tester...
>
Is that documented anywhere? I will remove this worker.
Thanks,
--
Paulo Matos