From: Paulo Matos <pmatos@linki.tools>
To: Markus Trippelsdorf <markus@trippelsdorf.de>,
Christophe Lyon <christophe.lyon@linaro.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC Buildbot Update
Date: Fri, 15 Dec 2017 09:21:00 -0000 [thread overview]
Message-ID: <de912f33-9bbd-b1a4-8d70-a9e354712abe@linki.tools> (raw)
In-Reply-To: <20171215074218.GA17463@x4>
On 15/12/17 08:42, Markus Trippelsdorf wrote:
>
> I don't think this is good news at all.
>
As I pointed out in a reply to Chris, I haven't seeked permission but I
am pretty sure something similar runs in the CF machines from other
projects.
The downside is that if we can't use the CF, I have no extra machines to
run the buildbot on.
> 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.
>
I understand your concern though. Do you know who this issue could be
raised with? FSF?
--
Paulo Matos
next prev parent reply other threads:[~2017-12-15 9:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 8:56 Paulo Matos
2017-12-14 11:39 ` David Malcolm
2017-12-15 9:16 ` Paulo Matos
2017-12-15 14:29 ` David Malcolm
2017-12-16 11:07 ` Paulo Matos
2018-01-24 19:20 ` jamais-vu can now ignore renumbering of source lines in dg output (Re: GCC Buildbot Update) David Malcolm
2018-01-25 7:25 ` Paulo Matos
2018-01-29 13:55 ` Paulo Matos
2018-01-29 14:19 ` David Malcolm
2018-01-29 14:27 ` Paulo Matos
2017-12-14 20:32 ` GCC Buildbot Update Christophe Lyon
2017-12-15 7:42 ` Markus Trippelsdorf
2017-12-15 9:21 ` Paulo Matos [this message]
2017-12-15 11:10 ` Markus Trippelsdorf
2017-12-15 17:05 ` Segher Boessenkool
2017-12-16 11:54 ` Paulo Matos
2017-12-15 9:19 ` Paulo Matos
2017-12-15 9:21 ` Christophe Lyon
2017-12-15 9:29 ` Paulo Matos
2017-12-20 8:32 ` Paulo Matos
2017-12-20 9:52 ` Christophe Lyon
2017-12-20 10:02 ` Paulo Matos
2017-12-20 10:09 ` Christophe Lyon
2017-12-20 11:49 ` James Greenhalgh
2017-12-20 14:01 ` Paulo Matos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de912f33-9bbd-b1a4-8d70-a9e354712abe@linki.tools \
--to=pmatos@linki.tools \
--cc=christophe.lyon@linaro.org \
--cc=gcc@gcc.gnu.org \
--cc=markus@trippelsdorf.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).