From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: thune.a.tran@boeing.com, Chuck Wolber <chuckwolber@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>, "Wolber (US),
Chuck" <chuck.wolber@boeing.com>
Subject: Re: [OE-core] [PATCH] oeqa/sdk/sdktest: Add test discovery across layers
Date: Thu, 17 Apr 2025 14:03:12 +0100 [thread overview]
Message-ID: <34381df1e0f5da0ba1e4512afc83fc1a99e9e54e.camel@linuxfoundation.org> (raw)
In-Reply-To: <SA1P110MB22506DADB11B27B51A1CC536B7BCA@SA1P110MB2250.NAMP110.PROD.OUTLOOK.COM>
On Thu, 2025-04-17 at 12:54 +0000, Thune Tran via lists.openembedded.org wrote:
> > On Wed, 2025-04-16 at 21:39 -0700, Chuck Wolber wrote:
> > > On Wed, Apr 16, 2025 at 3:07 PM Richard Purdie via
> > > lists.openembedded.org
> > > <richard.purdie=linuxfoundation.org@lists.openembedded.org> wrote:
> > >
> > > %< SNIP $<
> > > >
> > > > I suspect this causes some regressions in our automated testing
> > > > unfortunately:
> > > >
> > > > buildtools:
> > > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/43/builds/1
> > > > 396
> > > >
> > > > meta-mingw:
> > > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/7/builds/14
> > > > 30
> > > >
> > >
> > >
> > > Would it make more sense to add
> > > self.context_executor_class.default_cases
> > > to the list of paths returned by get_sdk_paths?
> >
> > meta/recipes-core/meta/buildtools-tarball.bb does:
> >
> > cases_path =
> > os.path.join(os.path.abspath(os.path.dirname(oeqa.sdk.testsdk.__file__)),
> > d.getVar("TESTSDK_CASES"))
> > testsdk.context_executor_class.default_cases = cases_path
> > mingw does things in a different place, setting:
> >
> > default_cases = [os.path.join(os.path.abspath(os.path.dirname(__file__)),
> > 'cases')]
> >
> > in meta-mingw/lib/oeqa/sdkmingw/contex.py
> >
> > I think we need to add something which represents the name of the
> > directory for cases, i.e. "sdk", "sdkming", "sdk/buildtools-cases" and
> > then allow this to be passed into your function so regardless, it allows
> > customisation within a layer.
> We can match the test directory pattern (sdk, sdkming, sdk/buildtools-cases)
> found in default_cases. The test discovery will then be based on the matched pattern.
>
We could do that but in this case I think it might be better to improve
the code and make it a bit cleaner if we can, even if that is a little
more invasive.
This area of the code could do with simplification/cleanup...
Cheers,
Richard
next prev parent reply other threads:[~2025-04-17 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 16:41 [PATCH] oeqa/sdk/sdktest: Add test discovery across layers Thune Tran
2025-04-16 17:23 ` [OE-core] " Gyorgy Sarvari
2025-04-16 20:54 ` Tran (US), Thune A
2025-04-16 21:16 ` Gyorgy Sarvari
2025-04-16 22:07 ` Richard Purdie
2025-04-17 4:39 ` Chuck Wolber
2025-04-17 10:06 ` Gyorgy Sarvari
2025-04-17 11:04 ` Richard Purdie
2025-04-17 12:54 ` Tran (US), Thune A
2025-04-17 13:03 ` Richard Purdie [this message]
2025-04-17 15:53 ` Tran (US), Thune A
[not found] ` <18372610739395C0.11203@lists.openembedded.org>
2025-04-21 19:21 ` Tran (US), Thune A
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=34381df1e0f5da0ba1e4512afc83fc1a99e9e54e.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=chuck.wolber@boeing.com \
--cc=chuckwolber@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=thune.a.tran@boeing.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