All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Kral <sk@typedivision.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] oeqa: enable testresults.json for testexport
Date: Wed, 11 Mar 2020 21:38:00 +0100	[thread overview]
Message-ID: <d950b7b1-b5f1-8395-69d8-dde1d17725a8@typedivision.de> (raw)
In-Reply-To: <c487b390822a86c1f5dd9339324e86c973142e0e.camel@linuxfoundation.org>

Hi Richard,

I just started to evaluate the use of testexport.

If you think about removing that feature, what is the preferred way to 
test a deployed target image?
The idea here is to have two separate pipelines:

1. build
- a target-image-test (same as target-image but additional test 
facilities enabled, like ptest)
- the testexport output

2. test
- fetch build results and install the target-image-test to the real hardware
- run the exported runtime tests (host and target based cases)
- check/save the generated testresults.json

BR
Stefan

Am 11.03.20 um 18:22 schrieb Richard Purdie:
> On Wed, 2020-03-11 at 17:37 +0100, Stefan Kral wrote:
>> Add the option --json-result-dir to oeqa core context to enable
>> testresults.json creation for test runs via testexport.
>>
>> Eg. oe-test runtime --json-result-dir .
>>
>> Signed-off-by: Stefan Kral <sk@typedivision.de>
> Out of interest are you actively using testexport? I've been wondering
> if we should remove that support as it does complicate the code a lot
> and ironically, isn't well tested.
>
> Cheers,
>
> Richard
>



  reply	other threads:[~2020-03-11 20:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 16:37 [PATCH] oeqa: enable testresults.json for testexport Stefan Kral
2020-03-11 17:22 ` Richard Purdie
2020-03-11 20:38   ` Stefan Kral [this message]
2020-03-11 20:46     ` Alexander Kanavin
2020-03-11 21:27       ` Stefan Kral
2020-03-12  8:23         ` Alexander Kanavin
2020-03-12  9:12 ` Richard Purdie

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=d950b7b1-b5f1-8395-69d8-dde1d17725a8@typedivision.de \
    --to=sk@typedivision.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.