public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Cc:, Mark Wielaard <>
Subject: [builder] gdb_check_step: remove gdb.gdb/selftest.exp
Date: Wed,  8 Jun 2022 20:51:38 +0200	[thread overview]
Message-ID: <> (raw)


I just committed the following update to builder:

    selftest.exp is bad (flaky), just keep the gdb and gdbserver
    unittest.exp for the CI runs. does two builds for gdb.  quick CI builds that
just build gdb and gdb-server and run a small amount of tests that are
known to reliably PASS. If any of this fails it will sent email to the
gdb-testers mailinglist and the author of the commit.

It also does full builds for binutils-gdb as a whole plus the full
testsuite both against gcc and clang. These do record all logs in
bunsendb but doesn't sent emails:

With the removal of the selftest.exp there are only two unittest.exp
tests (one for gdb and one for gdbserver). This does seem very
minimal. Could someone suggest stable, known good passing tests that
should be added because when they do start failing it really is a
regression that should be flagged?

Note that the intention is to also allow a trybot that runs the same
set of CI tests so it can be used as pre-commit check.



P.S. There were same bad failing emails today. Our apologies, that was
a bunsen upload typo.

 builder/master.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/builder/master.cfg b/builder/master.cfg
index 852322f..af4f65f 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -1446,7 +1446,6 @@ gdb_check_step = steps.Test(
                  ("TESTS= "
-                  "gdb.gdb/selftest.exp "
                   "gdb.gdb/unittest.exp "
                   "gdb.server/unittest.exp ")],
         name='make check-gdb',

             reply	other threads:[~2022-06-08 18:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 18:51 Mark Wielaard [this message]
2022-06-09  9:37 ` Luis Machado
2022-06-09 23:09   ` Mark Wielaard
2022-06-09 23:21     ` Mark Wielaard
2022-06-10 10:50       ` Mark Wielaard
2022-06-10 10:58         ` Luis Machado
2022-06-10 15:17           ` will schmidt
2022-06-10 15:54           ` Carl Love
2022-06-10 19:11             ` Mark Wielaard
2022-06-10 20:11               ` Carl Love
2022-06-10 22:23                 ` Frank Ch. Eigler
2022-06-29 15:58               ` Carl Love
2022-06-29 22:42                 ` Mark Wielaard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).