public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Mark Wielaard <mark@klomp.org>,
	binutils@sourceware.org, overseers@sourceware.org,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Adding binutils to the GNU Toolchain buildbot on sourceware
Date: Mon, 25 Apr 2022 11:37:00 +0100	[thread overview]
Message-ID: <c122a146-dbec-ca73-0871-2ff234f82cf2@arm.com> (raw)
In-Reply-To: <YmZkKRO+yUHeFqV0@wildebeest.org>

On 4/25/22 10:04, Mark Wielaard wrote:
> Hi,
> 
> I was talking to Nick what the best way was to add binutils to the
> buildbot at https://builder.sourceware.org/. We came up with the
> following which tests a minimal setup on a somewhat older but stable
> distro:
> 
> - Debian 10, x86_64 which has Linux 4.19.235, GLIBC 2.28, gcc 8.3.0
>    GNU and Binutils 2.31.1
> 
> - Only triggers a build when any files under bfd/ binutils/ gas/ ld/
>    gold/ elfcpp/ include/ libiberty/ opcodes/ or the top-level
>    configure or Makefile.in changes.
> 
> - configure --enable-gold --enable-shared --enable-target=all
> 
> - make all-gas all-ld all-binutils all-gold
> 
> - make check-ld check-gas check-binutils
> 
> - log files ld/ld.{log,sum} gas/testsuite/gas.{log,sum}
>    binutils/binutils.{log,sum}
> 
> - Sents email to this list and any committers when the build changes
>    from sucess to failure (or back).
> 
> All of this can of course be changed/extended.
> There are other distros/arches available:
> https://builder.sourceware.org/buildbot/#/workers
> And we hope to add container based workers to support even more
> distros.
> 
> We only build a smaller set of tools to make sure you get a
> notification within 10 minutes if anything was broken (or fixed). We
> do build gold, but don't test it because the testsuite isn't
> zero-fail.
> 
> If you want Frank also has scripts to add the log files to bunsen.
> 
> The intention was that this was a zero-fail testsuite subset
> (gas,ld,binutils) but we did find two ld test failures:
> FAIL: Run p_align-1b with PIE
> FAIL: Run p_align-1d with -Wl,-z,max-page-size=0x1000 with PIE
> These tests seem to rely on a specific glibc version/bug fix. Nick is
> working on a fix.
> 
> Please let me know if any if this should be changed. The intention is
> that the buildbot will help with maintaining binutils, keep it
> building and zero-fail. If it isn't doing that, but get annoying let
> change the configuration.
> 
> Cheers,
> 
> Mark

As a general comment, I think we should have a single buildbot entry for 
the whole of binutils-gdb.

Given changes to bfd and opcodes can affect gdb, why not build gdb 
alongside the other tools? You don't need to run the gdb testsuite, 
which should make things much more deterministic.

I don't expect the build times including gdb/gdbserver/sim will be much 
longer.

  reply	other threads:[~2022-04-25 10:37 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25  9:04 Mark Wielaard
2022-04-25 10:37 ` Luis Machado [this message]
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
2022-04-28 16:28                   ` Mark Wielaard
2022-05-01 16:37                     ` binutils builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) Mark Wielaard
2022-05-05  7:53                       ` Jan Beulich
2022-05-07 20:25                         ` Mark Wielaard
2022-05-16  9:40                       ` 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=c122a146-dbec-ca73-0871-2ff234f82cf2@arm.com \
    --to=luis.machado@arm.com \
    --cc=binutils@sourceware.org \
    --cc=gdb@sourceware.org \
    --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).