From: Mark Wielaard <mark@klomp.org>
To: Ben Woodard <woodard@redhat.com>
Cc: Ben Woodard via Libabigail <libabigail@sourceware.org>
Subject: Re: Fwd: Testing Setup - More Tests and Automation?
Date: Thu, 28 Apr 2022 10:06:59 +0200 [thread overview]
Message-ID: <YmpLI/I8/I0/Bm2J@wildebeest.org> (raw)
In-Reply-To: <34E58964-E930-4DF9-87CD-18D4C63DBCEB@redhat.com>
Hi,
On Wed, Apr 27, 2022 at 05:55:07PM -0700, Ben Woodard via Libabigail wrote:
> I personally feel like we need to reconsider
> https://sourceware.org/pipermail/libabigail/2022q1/004045.html and
> have checks like this built into the normal “make check” having
> ENABLE_SLOW_TEST=no by default allows too many bugs to creep
> in. People don’t use it. As a case in point neither the current
> trunk or the fixes branch pass all the tests when it is set.
We could/should probably add ENABLE_SLOW_TEST=yes to the buildbot.
The builder recently got moved to the general sourceware GNU Toolchain
https://builder.sourceware.org/ with configuration/sources here
https://sourceware.org/git/builder.git
The builder doesn't do containers builds nor pre-commit builds, but
that is on the TODO list.
Cheers,
Mark
next prev parent reply other threads:[~2022-04-28 8:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM=pu++-JdBdizXQ9dj8eUypXg7fpPOTDzN6BL1NY-TFvk++kQ@mail.gmail.com>
2022-04-28 0:55 ` Ben Woodard
2022-04-28 1:57 ` v
2022-04-30 19:55 ` Mark Wielaard
2022-04-30 20:36 ` v
2022-04-30 21:48 ` Mark Wielaard
2022-04-30 22:38 ` v
2022-05-01 22:42 ` Mark Wielaard
2022-05-01 22:46 ` v
2022-06-09 11:31 ` Thinking different (was Re: Testing Setup - More Tests and Automation?) Dodji Seketeli
2022-06-09 19:48 ` v
2022-06-15 14:21 ` Dodji Seketeli
2022-06-09 11:18 ` Testing Setup - More Tests and Automation? Dodji Seketeli
2022-06-09 11:11 ` Dodji Seketeli
2022-06-14 10:05 ` Mark Wielaard
2022-04-28 8:06 ` Mark Wielaard [this message]
2022-04-29 21:13 ` Fwd: " Mark Wielaard
2022-04-29 22:02 ` Mark Wielaard
2022-05-03 19:08 ` Ben Woodard
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=YmpLI/I8/I0/Bm2J@wildebeest.org \
--to=mark@klomp.org \
--cc=libabigail@sourceware.org \
--cc=woodard@redhat.com \
/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).