On 2017.10.11 at 08:22 +0200, Paulo Matos wrote: > > > 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.
Thanks. And while you are at it please set the niceness to 19. > > 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. https://community.amd.com/thread/215773 -- Markus
