From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Mark Wielaard <mark@klomp.org>
Cc: "Luis Machado" <luis.machado@arm.com>,
"Frank Ch. Eigler" <fche@elastic.org>,
"Dan Horák" <dhorak@redhat.com>,
"Overseers mailing list" <overseers@sourceware.org>,
binutils@sourceware.org,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Adding binutils to the GNU Toolchain buildbot on sourceware
Date: Thu, 28 Apr 2022 10:47:52 -0400 [thread overview]
Message-ID: <m3zgk5clif.fsf@fitzsim.org> (raw)
In-Reply-To: <20220428141957.GB23335@gnu.wildebeest.org> (Mark Wielaard's message of "Thu, 28 Apr 2022 16:19:57 +0200")
Hi Mark,
Mark Wielaard <mark@klomp.org> writes:
> On Thu, Apr 28, 2022 at 01:23:44PM +0100, Luis Machado wrote:
>> It would make sense to build-test gdb if any of the following changes:
>
> Thanks, updated the gdb_files list. Also added fedora-x86_64,
> debian-armhf, debian-arm64 and fedora-s390 builders. See attached.
>
> Tom, would it be OK to add a debian-ppc64 builder for gdb? As you can
> see in the master.cfg it only does a build of gdb and gdbserver for
> now, no tests are run. So it just would make sure that things
> build. We'll might add tests later, if we can figure out a sane subset
> that should always be green (and won't take more than a couple of
> minutes to run). BTW. I am also working on adding more builders for
> binutils (gas, ld, binutils) but the current testsuite doesn't seem
> clean on anything than latest fedora-x86_64.
OK, let's try it. The debian-ppc64 builder has 8 GiB of free disk
space.
Thomas
next prev parent reply other threads:[~2022-04-28 14:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YmZkKRO+yUHeFqV0@wildebeest.org>
2022-04-25 10:37 ` Luis Machado
2022-04-25 10:43 ` Frank Ch. Eigler
2022-04-25 12:16 ` Luis Machado
2022-04-25 12:30 ` Frank Ch. Eigler
2022-04-25 18:20 ` Mark Wielaard
2022-04-25 18:27 ` Frank Ch. Eigler
2022-04-25 22:11 ` Mark Wielaard
2022-04-26 3:33 ` Alan Modra
2022-04-26 6:22 ` Jan Beulich
2022-04-26 12:27 ` Nick Clifton
2022-04-26 13:49 ` Jan Beulich
2022-04-26 15:47 ` H.J. Lu
2022-04-27 6:15 ` Jan Beulich
2022-04-28 12:10 ` Nick Clifton
2022-04-28 13:07 ` Jan Beulich
2022-04-26 15:54 ` H.J. Lu
2022-04-26 23:33 ` Alan Modra
2022-04-27 18:32 ` [PATCH] x86: Disable 2 tests with large memory requirement H.J. Lu
2022-04-26 7:01 ` Adding binutils to the GNU Toolchain buildbot on sourceware Luis Machado
2022-04-26 9:40 ` Frank Ch. Eigler
2022-04-26 22:59 ` Mark Wielaard
2022-04-26 22:34 ` Mark Wielaard
2022-04-28 12:23 ` Luis Machado
2022-04-28 13:50 ` Frank Ch. Eigler
2022-04-28 13:53 ` Luis Machado
2022-04-28 14:22 ` Frank Ch. Eigler
2022-04-28 17:04 ` Mark Wielaard
2022-04-28 14:48 ` Mark Wielaard
2022-04-28 14:19 ` Mark Wielaard
2022-04-28 14:47 ` Thomas Fitzsimmons [this message]
2022-04-28 16:28 ` Mark Wielaard
2022-04-29 20:04 ` gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) Mark Wielaard
2022-05-01 19:44 ` Mark Wielaard
2022-05-03 15:41 ` Simon Marchi
2022-05-13 8:21 ` Mark Wielaard
2022-04-28 17:50 ` Adding binutils to the GNU Toolchain buildbot on sourceware Nick Alcock
2022-04-29 17:54 ` Mark Wielaard
2022-04-30 0:12 ` Nick Alcock
2022-04-30 22:27 ` Mark Wielaard
2022-05-03 12:48 ` Nick Alcock
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=m3zgk5clif.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=binutils@sourceware.org \
--cc=dhorak@redhat.com \
--cc=fche@elastic.org \
--cc=gdb@sourceware.org \
--cc=luis.machado@arm.com \
--cc=mark@klomp.org \
--cc=overseers@sourceware.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).