From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Luis Machado via Gdb <gdb@sourceware.org>
Subject: Re: [RFC] Proposal for hosting GDB CI builds
Date: Thu, 01 Jul 2021 14:08:39 +0200 [thread overview]
Message-ID: <ydd4kde1bjs.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <e53e457b-4842-50c7-aa64-115fc17159f9@linaro.org> (Luis Machado via Gdb's message of "Thu, 1 Jul 2021 08:50:07 -0300")
Hi Luis,
>> From the reports you shared above, it seems there are lots of tests
>> with "random" results (or rather lots of differences between two
>> runs). My fear is that reports will soon get ignored if there are too
>> many false regressions. But I hope that making such variations public
>> will help fix the root cause.
>
> Unfortunately that's always been the nature of GDB's testsuite. It has
> improved over the year, but there are still problematic tests. We will
> certainly have to put those into an exception list when reporting the
> summaries, at least at an initial stage.
on the Solaris side, things are considerably worse: there are currently
2000+ FAILs for a GDB testsuite run, with considerable variation between
reruns. I've never got a grip on what's going on, unfortunately, and in
the end turned the Solaris GDB buildbots to be build-only so I'd at
least catch build failures early.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2021-07-01 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 16:46 Luis Machado
2021-07-01 9:40 ` Rainer Orth
2021-07-01 11:48 ` Luis Machado
2021-07-01 12:06 ` Rainer Orth
2021-07-01 13:10 ` Luis Machado
2021-07-02 9:05 ` Rainer Orth
2021-07-01 11:37 ` Christophe LYON
2021-07-01 11:50 ` Luis Machado
2021-07-01 12:08 ` Rainer Orth [this message]
2021-07-20 15:21 ` Luis Machado
2021-07-23 20:17 ` Simon Marchi
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=ydd4kde1bjs.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb@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).