Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: Alex Kiernan <alex.kiernan@gmail.com>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] more ptest pedantry: why conditionally include "run-ptest" in SRC_URI?
Date: Mon, 12 Feb 2024 16:11:00 +0000	[thread overview]
Message-ID: <F448E74E-3EF8-4AED-B7C9-C61F300C0C44@arm.com> (raw)
In-Reply-To: <CAO5Uq5TYipCFncPuQFBXOr4BtLUDnsXGNr5w5OsyWjxXMpEZsQ@mail.gmail.com>

On 12 Feb 2024, at 15:00, Alex Kiernan <alex.kiernan@gmail.com> wrote:
> PTEST_ENABLED is just set in ptest.bbclass:
> 
> PTEST_ENABLED = "${@bb.utils.contains('DISTRO_FEATURES', 'ptest', '1', '0', d)}"
> PTEST_ENABLED:class-native = ""
> PTEST_ENABLED:class-nativesdk = ""
> PTEST_ENABLED:class-cross-canadian = ""
> 
> I'd argue checking PTEST_ENABLED is the right way.

Agreed, I’ve done exactly what you said before: ptest globally is off, but I can turn it on for specific recipes.  Or turn it on globally but then off for specific recipes.

Ross

  reply	other threads:[~2024-02-12 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  6:39 more ptest pedantry: why conditionally include "run-ptest" in SRC_URI? Robert P. J. Day
2024-02-12  6:47 ` Robert P. J. Day
2024-02-12 10:04   ` [OE-core] " Alexander Kanavin
2024-02-12 11:48 ` Ross Burton
2024-02-12 12:17   ` Robert P. J. Day
2024-02-12 12:55     ` Alex Kiernan
2024-02-12 14:46       ` Robert P. J. Day
2024-02-12 15:00         ` Alex Kiernan
2024-02-12 16:11           ` Ross Burton [this message]
2024-02-13 11:21             ` Robert P. J. Day
2024-02-13 16:25               ` Alex Kiernan
2024-02-13 11:35   ` Robert P. J. Day
2024-02-13 15:23     ` Peter Kjellerstedt

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=F448E74E-3EF8-4AED-B7C9-C61F300C0C44@arm.com \
    --to=ross.burton@arm.com \
    --cc=alex.kiernan@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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