public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz@gentoo.org>
To: "Maciej Barć" <xgqt@gentoo.org>,
	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 12:05:28 -0400	[thread overview]
Message-ID: <2149262c-83f5-4853-b0cb-dc23fc172a1d@gentoo.org> (raw)
In-Reply-To: <5be446de-361c-4d60-bf25-e9276b1520a0@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1205 bytes --]

On 8/9/24 11:59 AM, Maciej Barć wrote:
> 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.


installsources is not the same thing at all. That parses ELF files to
extract .c / .cpp etc source filenames from debuginfo to save them.

This thread is asking about the idea of compiling test programs and
installing the test executables so that you can run them later. You
absolutely cannot do that with a directory of .c files, for numerous
reasons including the fact that it only saves sources for files which
get installed anyway, but also because it does not install build system
files (meson.build, Makefile, CMakeLists.txt, etc).

P.S. See my gnome documentation link, it talks about git cloning too.

-- 
Eli Schwartz


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2024-08-09 16:05 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ć
2024-08-09 16:05   ` Eli Schwartz [this message]
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=2149262c-83f5-4853-b0cb-dc23fc172a1d@gentoo.org \
    --to=eschwartz@gentoo.org \
    --cc=arsen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=python@gentoo.org \
    --cc=sam@gentoo.org \
    --cc=xgqt@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