From: "Maciej Barć" <xgqt@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Sam James <sam@gentoo.org>
Cc: "Arsen Arsenović" <arsen@gentoo.org>, python@gentoo.org
Subject: Re: [gentoo-dev] Handling installed tests
Date: Fri, 9 Aug 2024 17:59:08 +0200 [thread overview]
Message-ID: <5be446de-361c-4d60-bf25-e9276b1520a0@gentoo.org> (raw)
In-Reply-To: <87ttftr9ay.fsf@gentoo.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1621 bytes --]
Hi Sam,
We have a "source" flag so maybe we could either use that or have
"test-source" BUT we also have FEATURES="installsources" ...so (if I
understand that feature correctly) we can just run test from
/usr/src/debug/${CATEGORY}/${PF}
But IMO I'd rather clone the project and run test from the clone.
Of source the drawback of installsources & git cloning is that emerge
does not run any modifications on the tests nor applies patches to them
nor buildsystem/testrunner used.
W dniu 9.08.2024 o 17:43, Sam James pisze:
> Hi,
>
> I'm currently working on packaging dtrace which doesn't (at least
> currently, may not ever) support running tests as non-root, but
> does support handling installing them for later manual use.
>
> This raises a question: how should we control installing such tests? How
> should the user request that?
>
> USE=test isn't suitable because:
> a) I generally expect it not to mutate the image;
> b) ago, rightly, based on this has a tinderbox check which looks for
> added/removed files when tests are enabled.
>
> I'd like to pick some name which is suitable for us to use elsewhere and
> it's not really a package-specific issue. Thoughts?
>
> Please assume the tests are large enough to justify conditional install
> and have additional dependencies.
>
> (This is arguably related to https://bugs.gentoo.org/867799 and so on
> wrt dev-lang/python always installing tests.)
>
> thanks,
> sam
--
Have a great day!
~ Maciej XGQT Barć
https://wiki.gentoo.org/wiki/User:Xgqt
9B0A 4C5D 02A3 B43C 9D6F D6B1 14D7 4A1F 43A6 AC3C
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 16315 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2024-08-09 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 15:43 [gentoo-dev] Handling installed tests Sam James
2024-08-09 15:55 ` Eli Schwartz
2024-08-09 15:59 ` Maciej Barć [this message]
2024-08-09 16:05 ` Eli Schwartz
2024-08-09 16:12 ` Michał Górny
2024-08-16 5:02 ` Joonas Niilola
2024-08-18 19:06 ` Sam James
2024-08-19 4:59 ` Joonas Niilola
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=5be446de-361c-4d60-bf25-e9276b1520a0@gentoo.org \
--to=xgqt@gentoo.org \
--cc=arsen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=python@gentoo.org \
--cc=sam@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