From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: alexis.lothore@bootlin.com
Cc: Openembedded-core@lists.openembedded.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [OE-Core][PATCH v3 4/4] core-image-ptest: append ptest directory to artifacts list
Date: Fri, 9 Jun 2023 09:52:03 +0300 [thread overview]
Message-ID: <ZILME/DYo6hUkXv0@nuoska> (raw)
In-Reply-To: <20230609064802.11777-5-alexis.lothore@bootlin.com>
Hi,
On Fri, Jun 09, 2023 at 08:48:02AM +0200, Alexis Lothor� via lists.openembedded.org wrote:
> From: Alexis Lothor� <alexis.lothore@bootlin.com>
>
> TESTIMAGE_FAILED_QA_ARTIFACTS is defined in testimage.bbclass with a
> minimal list of files to retrieve when a test fail. By appending the ptest
> directory only in core-image-ptest.bb, thanks to multiconfig feature used
> in the recipe, only failing ptests will lead to corresponding ptest
> artifacts retrieval, instead of all ptests artifacts retrieval.
>
> Signed-off-by: Alexis Lothor� <alexis.lothore@bootlin.com>
> ---
> meta/recipes-core/images/core-image-ptest.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/images/core-image-ptest.bb b/meta/recipes-core/images/core-image-ptest.bb
> index 90c26641ba3a..e1be81bb2666 100644
> --- a/meta/recipes-core/images/core-image-ptest.bb
> +++ b/meta/recipes-core/images/core-image-ptest.bb
> @@ -28,6 +28,7 @@ QB_MEM:virtclass-mcextend-lttng-tools = "-m 4096"
> QB_MEM:virtclass-mcextend-python3-cryptography = "-m 4096"
>
> TEST_SUITES = "ping ssh parselogs ptest"
> +TESTIMAGE_FAILED_QA_ARTIFACTS:append=" ${libdir}/${MCNAME}/ptest"
Why not += ? Also, spaces around =.
If :append is used, bbappend in other layers can not easily override
this variable.
Cheers,
-Mikko
next prev parent reply other threads:[~2023-06-09 6:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 6:47 [OE-Core][PATCH v3 0/4] add failed tests artifacts retriever alexis.lothore
2023-06-09 6:47 ` [OE-Core][PATCH v3 1/4] oeqa/core/runner: add helper to know about expected failures alexis.lothore
2023-06-09 6:48 ` [OE-Core][PATCH v3 2/4] oeqa/target/ssh: update options for SCP alexis.lothore
2023-06-09 6:48 ` [OE-Core][PATCH v3 3/4] testimage: implement test artifacts retriever for failing tests alexis.lothore
2023-06-09 6:48 ` [OE-Core][PATCH v3 4/4] core-image-ptest: append ptest directory to artifacts list alexis.lothore
2023-06-09 6:52 ` Mikko Rapeli [this message]
2023-06-09 7:24 ` Alexis Lothoré
2023-06-11 15:16 ` Alexander Kanavin
2023-06-11 15:48 ` Alex Kiernan
2023-06-15 7:03 ` Richard Purdie
2023-06-15 8:34 ` Mikko Rapeli
2023-06-15 9:05 ` Richard Purdie
2023-06-15 21:27 ` 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=ZILME/DYo6hUkXv0@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=alexandre.belloni@bootlin.com \
--cc=alexis.lothore@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
/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