From: Christophe Lyon <christophe.lyon@arm.com>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org
Subject: Re: Removing arm/aarch64 binutils and gcc buildbots
Date: Mon, 2 Oct 2023 09:56:02 +0200 [thread overview]
Message-ID: <c6aabf70-1173-5eb4-c19b-7d2c87edbec2@arm.com> (raw)
In-Reply-To: <20230929131844.GF20136@gnu.wildebeest.org>
On 9/29/23 15:18, Mark Wielaard wrote:
> Hi Christophe,
>
> On Fri, Sep 29, 2023 at 11:31:21AM +0200, Christophe Lyon wrote:
>> After internal discussions following the CI presentations during the GNU
>> Cauldron, we have decided to allocate our arm & aarch64 builder to
>> Linaro CI.
>
> Some of the scripts that Maxim wrote for bisecting regressions are
> very exciting. I hope we can reuse them eventually.
>
Sure! All the sources are public on Linaro's git.
>> In practice, it means we would like to stop the binutils and gcc
>> buildbots (expect the gdb one to follow shortly, but it seems to use
>> very few resources at the moment, so we can try to keep it a little bit
>> more).
>>
>> I think you have to update the buildbot master config, before I stop the
>> corresponding containers?
>
> I have pushed the attached patch to remove them.
Thanks!
Christophe
>
> Cheers,
>
> Mark
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
prev parent reply other threads:[~2023-10-02 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 9:31 Christophe Lyon
2023-09-29 13:18 ` Mark Wielaard
2023-10-02 7:56 ` Christophe Lyon [this message]
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=c6aabf70-1173-5eb4-c19b-7d2c87edbec2@arm.com \
--to=christophe.lyon@arm.com \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.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).