From: Paulo Matos <pmatos@linki.tools>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Christophe Lyon <christophe.lyon@linaro.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC Buildbot Update
Date: Sat, 16 Dec 2017 11:54:00 -0000 [thread overview]
Message-ID: <e8d4d027-5b9a-7bcc-1def-dfaacd1d4780@linki.tools> (raw)
In-Reply-To: <20171215170514.GI10515@gate.crashing.org>
On 15/12/17 18:05, Segher Boessenkool wrote:
> All the cfarm machines are shared resources. Benchmarking on them will
> not work no matter what. And being a shared resource means all users
> have to share and be mindful of others.
>
Yes, we'll definitely need better machines for benchmarking. Something I
haven't thought of yet.
>> 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.
>
> The aarch64 builds should probably not use all of gcc113..gcc116.
>
> We do not have enough resources to dedicate machines to bots.
>
I have disabled gcc116.
Thanks,
--
Paulo Matos
next prev parent reply other threads:[~2017-12-16 11:54 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
2017-12-15 11:10 ` Markus Trippelsdorf
2017-12-15 17:05 ` Segher Boessenkool
2017-12-16 11:54 ` Paulo Matos [this message]
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=e8d4d027-5b9a-7bcc-1def-dfaacd1d4780@linki.tools \
--to=pmatos@linki.tools \
--cc=christophe.lyon@linaro.org \
--cc=gcc@gcc.gnu.org \
--cc=markus@trippelsdorf.de \
--cc=segher@kernel.crashing.org \
/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).