public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Luis Machado <luis.machado@arm.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>,
	Overseers mailing list <overseers@sourceware.org>,
	binutils@sourceware.org
Subject: Re: Adding binutils to the GNU Toolchain buildbot on sourceware
Date: Thu, 28 Apr 2022 19:04:54 +0200	[thread overview]
Message-ID: <20220428170454.GE23335@gnu.wildebeest.org> (raw)
In-Reply-To: <20220428142206.GH11115@redhat.com>

Hi Frank,

On Thu, Apr 28, 2022 at 10:22:06AM -0400, Frank Ch. Eigler via Binutils wrote:
> (The fedora-rawhide x86-64 builder
> I just started operating runs all the testsuites on all changes to
> binutils-gdb, taking about 90 minutes per build.  I have no problem
> with that.)

That is of course fine if the worker maintainer (you) is OK with
that. But do note that since your worker also runs other builders,
those buildsets might have to wait for those longer builds to
finish. e.g. at the moment there is a binutils-fedrawhide-x86_64 build
waiting for 6 hours now:
https://builder.sourceware.org/buildbot/#/pendingbuildrequests

And it might be in the queue for a couple more. It will eventually get
triggered, but it means the changeset for that buildset only gets a
report on failure (change) after a couple of hours. Which is why I
would like you to consider swapping that builder to another fedora
worker that is less overloaded. That way committers to binutils will
get a report earlier if something breaks. See my proposed patch at:
https://sourceware.org/pipermail/binutils/2022-April/120561.html

BTW. If you haven't done so yet (and you have the disk space) try
installing ccache on your worker. It drastically reduces build times
since patches normally only change a few source files and the ccache
will save you from recompiling everything.

Also you can consider setting collapseRequests=True on the
binutils_gdb_fedrawhide_x86_64_builder to collapse changes into one
build to keep the number of pending builds shorter:
https://docs.buildbot.net/latest/manual/configuration/builders.html#collapsing-build-requests

Cheers,

Mark

  reply	other threads:[~2022-04-28 17:04 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 [this message]
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-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=20220428170454.GE23335@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=fche@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=luis.machado@arm.com \
    --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).