From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Handling optional, expensive variants of test suite
Date: Fri, 09 Aug 2024 16:40:31 +0100 [thread overview]
Message-ID: <87zfplr9g0.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
Hi!
Some packages like libffi, gcc support extended, slower versions of
their testsuites. In the past, I've seen both USE="expensive-tests" (I
think) and USE="test-full" (used in a few places in-tree atm) for this.
I sort of hate both suggestions but I'm open to what people think is
best, with a view to then making it a global USE flag then? Thoughts?
Note that I _do_ think there's value in exposing these because some of
the configurations I use, and I know others are deploying Gentoo for,
are where they want to make use of as many opportunities as possible
to find bad runtime behaviour (kernel and toolchain patching).
thanks,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next reply other threads:[~2024-08-09 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 15:40 Sam James [this message]
2024-08-09 15:47 ` [gentoo-dev] Handling optional, expensive variants of test suite Pacho Ramos
2024-08-16 5:05 ` Joonas Niilola
2024-08-16 15:40 ` Andrey Grozin
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=87zfplr9g0.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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