From: Yao Qi <qiyaoltc@gmail.com>
To: pmatos@linki.tools
Cc: gcc@gcc.gnu.org, GDB <gdb@sourceware.org>,
Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Both GCC and GDB buildbot use gcc114
Date: Tue, 27 Feb 2018 12:53:00 -0000 [thread overview]
Message-ID: <CAH=s-PPFvDyaBrVE7tRrNstKnU-pjTDe1tdYA5qfxdWmR+0oQQ@mail.gmail.com> (raw)
Hi Paulo,
I noticed that GDB buildbot pending build queue on aarch64-linux
becomes longer and longer,
https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-m64
as it takes longer to finish each build and test.
Looks that you deployed aarch64-linux buildslave for GCC buildbot
on gcc114 as well, that is reason that GDB build and test is slowed
down (GCC build and test is slowed down too).
We'd better avoid using the same machine for two buildbots. Are there
any easy way to move one buildslave to a different machine like gcc115
or gcc116. As far as I know, they are identical.
--
Yao (齐尧)
next reply other threads:[~2018-02-27 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 12:53 Yao Qi [this message]
2018-02-27 21:46 ` Paulo Matos
2018-02-28 9:12 ` Yao Qi
2018-03-01 12:41 ` Add .gdb_index and CRC mismatch Dmitry Antipov
2018-03-01 21:05 ` Jan Kratochvil
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='CAH=s-PPFvDyaBrVE7tRrNstKnU-pjTDe1tdYA5qfxdWmR+0oQQ@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=pmatos@linki.tools \
--cc=sergiodj@redhat.com \
/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