From: "Frank Ch. Eigler" <fche@elastic.org>
To: Luis Machado <luis.machado@arm.com>
Cc: Mark Wielaard <mark@klomp.org>,
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: Tue, 26 Apr 2022 05:40:25 -0400 [thread overview]
Message-ID: <Yme+CQiyCk0t/BX2@elastic.org> (raw)
In-Reply-To: <524b04b7-a78c-7aae-4605-b40f61e6830c@arm.com>
Hi -
> I agree with the quick build idea. That's why I suggested only making sure
> gdb/gdbserver/sim builds properly. That's reasonably reliable.
OK, so looking for build-breaking regressions.
> 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.
> > If the is a make check-something that can be executed quickly, < 5
> > minutes runtime, and that should always be green please include
> > it. But please exclude anything that takes too long, isn't known
> > all-green or contains flaky tests.
>
> Some tests should always work, no matter what. We could hand-pick some tests
> from the GDB testsuite that we consider critical. [...]
Bunsen should help -identify- such tests.
- FChE
next prev parent reply other threads:[~2022-04-26 9:40 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 [this message]
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
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=Yme+CQiyCk0t/BX2@elastic.org \
--to=fche@elastic.org \
--cc=binutils@sourceware.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).