This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC Buildbot Update
- From: Markus Trippelsdorf <markus at trippelsdorf dot de>
- To: Christophe Lyon <christophe dot lyon at linaro dot org>
- Cc: Paulo Matos <pmatos@linki.tools>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Fri, 15 Dec 2017 08:42:18 +0100
- Subject: Re: GCC Buildbot Update
- Authentication-results: sourceware.org; auth=none
- References: <f664b74e-8751-24ed-139f-443ce3f1cdef@linki.tools> <CAKdteObvKKTJrpq2Mod-9H37QpiT2gPshgfeztWJvi-XLQE-sw@mail.gmail.com>
On 2017.12.14 at 21:32 +0100, Christophe Lyon wrote:
> On 14 December 2017 at 09:56, Paulo Matos <pmatos@linki.tools> wrote:
> > I got an email suggesting I add some aarch64 workers so I did:
> > 4 workers from CF (gcc113, gcc114, gcc115 and gcc116);
> >
> Great, I thought the CF machines were reserved for developpers.
> Good news you could add builders on them.
I don't think this is good news at all.
Once a buildbot runs on a CF machine it immediately becomes impossible
to do any meaningful measurement on that machine. That is mainly because
of the random I/O (untar, rm -fr, etc.) of the bot. As a result variance
goes to the roof and all measurements drown in noise.
So it would be good if there was a strict separation of machines used
for bots and machines used by humans. In other words bots should only
run on dedicated machines.
--
Markus