public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Handling optional, expensive variants of test suite
Date: Fri, 09 Aug 2024 17:47:48 +0200	[thread overview]
Message-ID: <0707945f50069b6ab52614ed3cb7c6103478c2eb.camel@gentoo.org> (raw)
In-Reply-To: <87zfplr9g0.fsf@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

El vie, 09-08-2024 a las 16:40 +0100, Sam James escribió:
> 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

Hi!

I would opt for "test-full" as it looks for descriptive to me.
"expensive" will have different meanings (expensive in memory, CPU,
disk usage?) that are also likely to change in the future (for example,
needing 4Gb of RAM to run is probably less "expensive" now than ten
years ago).

In any case, if you prefer other terms, no problem.

Regards

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-08-09 15:47 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 [this message]
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=0707945f50069b6ab52614ed3cb7c6103478c2eb.camel@gentoo.org \
    --to=pacho@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