From: Mark Wielaard <mark@klomp.org>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Cc: "Overseers mailing list" <overseers@sourceware.org>,
"Thomas Fitzsimmons" <fitzsim@fitzsim.org>,
"Dan Horák" <dhorak@redhat.com>,
"Frank Ch. Eigler" <fche@elastic.org>
Subject: Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware)
Date: Fri, 13 May 2022 10:21:16 +0200 [thread overview]
Message-ID: <6ee4c888c35b58b48ddb3c5fac21a99a439cbad9.camel@klomp.org> (raw)
In-Reply-To: <20220429200422.GB7305@gnu.wildebeest.org>
Hi gdb hackers,
On Fri, 2022-04-29 at 22:04 +0200, Mark Wielaard wrote:
> https://builder.sourceware.org now has 6 build only builders.
> centos-x86_64, fedora-x86_64, debian-armhf, debian-arm64, fedora-s390x and debian-ppc64.
> I like to add a fedora-ppc64le one once that one has enough disk space.
>
> These builders are fairly quick, a few minutes at most. And all except
> the fedora-s390x one build fine. They should sent email once a new
> failure occurs.
> [...]
> There is also one build and check everything builder
> https://builder.sourceware.org/buildbot/#/builders/binutils-gdb-fedrawhide-x86_64
> I haven't looked at the test results yet, but they are all stored in
> the bunsendb.git for later analysis. This builder doesn't sent emails
> on bad builds.
>
> One issue with the build-check-everything builder might be the widely
> varying build times which range from 1 to 7 hours.
There are now 7 "quick" CI builders:
https://builder.sourceware.org/buildbot/#/builders?tags=gdb
gdb-fedora-ppc64le has been added, which failed to compile at first,
but that has been fixed now. Also it does a very minimal make gdb-check
now:
# Only a small subset of tests that are fast and known to PASS.
gdb_factory.addStep(steps.Test(
workdir='gdb-build',
command=['make',
util.Interpolate('-j%(prop:ncpus)s'),
'check-gdb',
("TESTS= "
"gdb.gdb/selftest.exp "
"gdb.gdb/unittest.exp "
"gdb.server/unittest.exp ")],
name='make check-gdb',
logfiles={ "gdb.sum": "gdb/testsuite/gdb.sum",
"gdb.log": "gdb/testsuite/gdb.log" },
haltOnFailure=True))
There was some skepticism on irc that this could ever be expanded to a
set of tests that was really useful. But I am keeping some hope. And
even the compile only part already caught bad commits, so I do think it
is useful. My goal is to turn these builders into try-builders at some
point so people can submit patches and see they at least pass a compile
and test for a reasonable (fast) subset without having to go through
known failing or flaky testcases.
Also Frank seems to have gotten a handle on the widely varying full
tests builds. They seem to take about ~1 hour each now. And he added a
full "clang" builder so you can more easily compare test results with
an alternative compiler:
https://builder.sourceware.org/buildbot/#/builders/binutils-gdb-fedrawhide-x86_64
https://builder.sourceware.org/buildbot/#/builders/binutils-gdb-clang-fedrawhide-x86_64
The sum and log files are put into the bunsendb.git repository. Only
the stdio output is available in the builder itself for now.
Cheers,
Mark
next prev parent reply other threads:[~2022-05-13 8:21 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 ` Adding binutils to the GNU Toolchain buildbot on sourceware 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
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 [this message]
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=6ee4c888c35b58b48ddb3c5fac21a99a439cbad9.camel@klomp.org \
--to=mark@klomp.org \
--cc=dhorak@redhat.com \
--cc=fche@elastic.org \
--cc=fitzsim@fitzsim.org \
--cc=gdb@sourceware.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).