From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>,
openembedded-core@lists.openembedded.org,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 3/3] selftest/sstatetests: add a test for CDN sstate cache
Date: Thu, 26 Oct 2023 13:10:46 +0100 [thread overview]
Message-ID: <3e070cec102dfcb3bcd30b10f445f8b40796ba5b.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8+FTOO4cDsPzE_g4Hdfw7qtHvnYvK1WwFYdRRLKhJbWA@mail.gmail.com>
On Thu, 2023-10-26 at 13:32 +0200, Alexander Kanavin wrote:
> On Thu, 26 Oct 2023 at 13:26, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > > We need to think of ways to test/debug this that don't require running a-full.
> >
> > We can create a separate target (builder) on the AB to just run the
> > test?
>
> But it needs to run just after the task (e.g. world or some other
> which should be dynamically specified) that is supposed to create the
> required objects. I guess it needs to be done with a custom branch on
> yocto-autobuilder-helper which would define that, but then how to
> trigger it through the UI?
We could run the appropriate build and then the test in the next step?
It could be a standalone builder target which just isn't triggered by
default? Not all targets have to be triggered by something day to day.
Cheers,
Richard
next prev parent reply other threads:[~2023-10-26 12:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 11:06 [PATCH 1/3] selftest/sstatetests: add tests for 'bitbake -S printdiff' Alexander Kanavin
2023-10-23 11:06 ` [PATCH 2/3] lib/oe/sstatesig.py: dump locked.sigs.inc only when explicitly asked via -S lockedsigs Alexander Kanavin
2023-10-23 11:06 ` [PATCH 3/3] selftest/sstatetests: add a test for CDN sstate cache Alexander Kanavin
2023-10-24 8:33 ` [OE-core] " Luca Ceresoli
2023-10-26 10:26 ` Alexander Kanavin
2023-10-26 10:53 ` Richard Purdie
2023-10-26 11:16 ` Alexander Kanavin
2023-10-26 11:26 ` Richard Purdie
2023-10-26 11:32 ` Alexander Kanavin
2023-10-26 12:10 ` Richard Purdie [this message]
2023-10-26 12:53 ` Richard Purdie
2023-10-26 14:36 ` Alexander Kanavin
2023-10-26 16:13 ` Richard Purdie
2023-10-27 12:54 ` Alexander Kanavin
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=3e070cec102dfcb3bcd30b10f445f8b40796ba5b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.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.