From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Luis Machado <luis.machado@arm.com>,
"Frank Ch. Eigler" <fche@elastic.org>,
"gdb@sourceware.org" <gdb@sourceware.org>,
binutils@sourceware.org
Subject: Re: Adding binutils to the GNU Toolchain buildbot on sourceware
Date: Wed, 27 Apr 2022 00:59:35 +0200 [thread overview]
Message-ID: <Ymh5V9W02KpMoFjm@wildebeest.org> (raw)
In-Reply-To: <Yme+CQiyCk0t/BX2@elastic.org>
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
Hi Frank,
On Tue, Apr 26, 2022 at 05:40:25AM -0400, Frank Ch. Eigler via Overseers wrote:
> > Unfortunately gdb's testsuite is not too reliable. It's been improved over
> > the years, but still gives quite a bit of non-deterministic results based on
> > distro version/compiler version etc. So I'd leave those out in favor of just
> > making sure things build properly.
>
> This problem is why we're building out a gadget called bunsen, which
> is a tool to absorb histories of testsuites, and draw statistical
> conclusions. Still early days, but noisy testsuites are not a
> problem.
Right. And because Keith is very involved with this having builders
that feed bunsen lots of gdb testsuite results is important. Sorry if
I made it sound like "large checks" aren't important for the
builder. They are!
But I do think we should try to split the "heavy test everything
builders" from the "quick sanity check builders" a bit.
e.g. maybe we can use the fedrawhide-x86_64 worker only for the full
gdb-binutils builder and use another worker for the "quick" binutils
only builder. That way a "quick" builder doesn't get behind a couple
of "heavy" builds (which means you might get your quick result only
after a couple of hours).
How about using the other fedora-x86_64 worker (as attached)?
I tried a couple of other workers, but some were too slow, or didn't
generate a clean make check-ld results.
Cheers,
Mark
[-- Attachment #2: binutils-fedora-x86_64.patch --]
[-- Type: text/x-diff, Size: 2409 bytes --]
diff --git a/builder/master.cfg b/builder/master.cfg
index 340904f..b706401 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -123,7 +123,7 @@ debian_ppc64_worker = worker.Worker("debian-ppc64",
'fitzsim@fitzsim.org']);
c['workers'].append(debian_ppc64_worker)
-# Power VM run by Tom on a Talos workstation
+# Frank's Fedora Rawhide builder
fedrawhide_x86_64_worker = worker.Worker("fedrawhide-x86_64",
getpw("fedrawhide-x86_64"),
max_builds=1,
@@ -374,7 +374,8 @@ binutils_scheduler = schedulers.SingleBranchScheduler(
change_filter=util.ChangeFilter(project="binutils-gdb",
branch="master"),
fileIsImportant=binutilsImportant,
- builderNames=["binutils-debian-amd64", "binutils-fedrawhide-x86_64"])
+ builderNames=["binutils-debian-amd64",
+ "binutils-fedora-x86_64"])
c['schedulers'].append(binutils_scheduler)
# Only trigger scheduler for changes to gdb (or deps)
@@ -1146,12 +1147,12 @@ binutils_debian_amd64_builder = util.BuilderConfig(
factory=binutils_factory)
c['builders'].append(binutils_debian_amd64_builder)
-binutils_fedrawhide_x86_64_builder = util.BuilderConfig(
- name="binutils-fedrawhide-x86_64",
- workernames=["fedrawhide-x86_64"],
+binutils_fedora_x86_64_builder = util.BuilderConfig(
+ name="binutils-fedora-x86_64",
+ workernames=["fedora-x86_64"],
tags=["binutils", "fedora", "x86_64"],
factory=binutils_factory)
-c['builders'].append(binutils_fedrawhide_x86_64_builder)
+c['builders'].append(binutils_fedora_x86_64_builder)
# gdb build steps, factory and builders
diff --git a/htdocs/index.html b/htdocs/index.html
index b08a17b..d732d5d 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -34,6 +34,8 @@
<td><a href="/buildbot/#/builders?tags=binutils">binutils</a></td>
<td><a href="/buildbot/#builders/binutils-debian-amd64">debian-amd64<br>
<img src="/buildbot/badges/binutils-debian-amd64.svg"></a></td>
+ <td><a href="/buildbot/#builders/binutils-fedora-x86_64">fedora-x86_64<br>
+ <img src="/buildbot/badges/binutils-fedora-x86_64.svg"></a></td>
</tr>
<tr>
<td><a href="/buildbot/#/builders?tags=bzip2">bzip2</a></td>
next prev parent reply other threads:[~2022-04-26 22:59 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 [this message]
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
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=Ymh5V9W02KpMoFjm@wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=fche@elastic.org \
--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).