From: Andrey Grozin <grozin@woodpecker.gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Handling optional, expensive variants of test suite
Date: Fri, 16 Aug 2024 15:40:06 +0000 (UTC) [thread overview]
Message-ID: <be6df904-d2fc-ea2c-e3fc-7e5ff061a582@woodpecker.gentoo.org> (raw)
In-Reply-To: <a2c10190-c74b-414f-bf13-60ae87c36631@gentoo.org>
On Fri, 16 Aug 2024, Joonas Niilola wrote:
> On 9.8.2024 18.40, Sam James wrote:
>> 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?
> Count NSS in that list too! I've made a patch locally that uses
> "tests-full" use flag, so I guess I'd vote for "test-full" to stay
> consistent.
Some tests of sympy take very long. They were commented out in the ebuild.
I'd like to have an easy way to run all tests.
Andrey
prev parent reply other threads:[~2024-08-16 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 15:40 [gentoo-dev] Handling optional, expensive variants of test suite Sam James
2024-08-09 15:47 ` Pacho Ramos
2024-08-16 5:05 ` Joonas Niilola
2024-08-16 15:40 ` Andrey Grozin [this message]
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=be6df904-d2fc-ea2c-e3fc-7e5ff061a582@woodpecker.gentoo.org \
--to=grozin@woodpecker.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