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

-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEE808Ng0g83FMNupoifLEMIH/AfbwFAma2OiQACgkQfLEMIH/A fbxOKwgAp8qJ6Lo1JellKVHASzeGzP/9sN5+8ffYEha4I5LPkiqpJ2BJJEqqTivb Ol/3gC2KzSqhhWWpPuLkPzgsfUe4YPP/MugWT4eSlW4jOg7ehwJYfvHEWnhw+KMD FvMIg0o9/DL3+QTICdVj20K+522Kdqo57BAS3cqdcW/lXuOru6+ez8R2KsLodGkQ iRs3mSBUdazsNg82hNsLPwL5+yYJooRbL18/6KNOgDofMETfTuYtBAlirJebhJGP YG4Gvo8x3MVLYhGVMI7P1Qqg/37XCjmNRkZ5N7lvQUTdRWhmk6SNLhcgQJZ+IC1P AW88lwL/g/w6rQZARtMu77GI0Ce9lA==
=9d91
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

-----BEGIN PGP SIGNATURE-----

iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZrY4b18UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZBMRwD/dFJ3G+GFHMfNd6111S9fX9WHn5BGTn33omsJ JDOEgEUBAPOCJV5wts/gDSqzCawg4c3e4OiGHMygiUHfxa/XsesM
=rPII
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------nARpTB7tq8RVt5bfsocqXQhK
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hey,

On 9.8.2024 18.40, Sam James wrote:

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?

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.

-- juippis

--------------nARpTB7tq8RVt5bfsocqXQhK--

-----BEGIN PGP SIGNATURE-----

iQGTBAEBCgB9FiEEltRJ9L6XRmDQCngHc4OUK43AaWIFAma+3ixfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk2 RDQ0OUY0QkU5NzQ2NjBEMDBBNzgwNzczODM5NDJCOERDMDY5NjIACgkQc4OUK43A aWI/FAf9FTEteY1DVZMhHQPtulefcOFng8H5z7h1+ErSCXCYTNVhnTUidzKmtjnV JWnq1LvfOIfhWwjN97PA5yzHya9qt3nSD1pjq4kItsI40nByVaHsb5H8/Efonak8 bPqYZ6u/uMPB+eJZWmqtCsj/ZWh09b3PhstpK7Kf3MULht1lL1ZCn5ADi9AGoIrT eU1vxcOBY6d7ZVlx+ILqo1foA3PgO58t40C4Mm/r7Dw+xMlUmKSK5ektfkxw+UTb h2+ihKD+hmSb/a7iLzGSaBjVu7Vyp2XPZTO0Ly+XR/b0f+0Rpe919QTzpb0MQwi2 LEFBjmRzJbnvLIm+vJ1uZptEZCt9pQ==
=UnYI
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)