All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Sean Anderson <sean.anderson@seco.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	 openembedded-core@lists.openembedded.org,
	Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: Re: [PATCH 6/6] u-boot: Rework signing to remove interdependencies
Date: Wed, 26 Oct 2022 18:00:06 +0100	[thread overview]
Message-ID: <514b492351ff6be577b80881adbc6b508fc04071.camel@linuxfoundation.org> (raw)
In-Reply-To: <dbd14d02-ad22-1036-d659-f71eb09a0e83@seco.com>

On Wed, 2022-10-26 at 12:49 -0400, Sean Anderson wrote:
> On 10/26/22 10:08, Richard Purdie wrote:
> > This looks like a pretty nice improvement, I've been worried about how
> > entangled all this was becoming. Is there anything better we could do
> > with testing of this code? We rely increasingly on the tests to spot
> > regressions and I doubt the testcases we have cover the code
> > complexity.
> 
> FWIW, I found the test suite to be fairly helpful when debugging this
> whole process, if agonizingly slow. I found many bugs in my initial
> implementation which were uncovered by the test suites,
> 
> The best way to extend the test suite would probably be to have QEMU try
> to boot using the Linux and U-Boot. This would help cases where all the
> artifacts are created correctly but e.g. the wrong U-Boot is packaged.
> However, I am rather loathe to add more test cases like this, because it
> already takes around 10 minutes (with sstate!) to run the tests. This
> basically kills the speed of iterative development.

Out of interest how were you running the tests? Did you look at the
parallelism options? Were you just running specific tests or specific
suites of tests?

I do think we need something like you describe and adding a linux+uboot
approach is something I've wanted to do for a long time. Usually the
time is taken on our automated CI rather than impacting users, unless
they're working in that area at which point the tests are hopefully
helpful.

We haven't really had anyone try and optimise the tests either, I'm
sure there will be things in there which can help. Please don't let the
speed put you off trying to improve things and extend our coverage!

Cheers,

Richard




  reply	other threads:[~2022-10-26 17:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 23:37 [PATCH 0/6] u-boot: Rework signing process to remove interdependencies Sean Anderson
2022-10-21 23:37 ` [PATCH 1/6] uboot-sign: Fix using wrong KEY_REQ_ARGS Sean Anderson
2022-10-21 23:37 ` [PATCH 2/6] kernel: Clear SYSROOT_DIRS instead of replacing sysroot_stage_all Sean Anderson
2022-10-21 23:37 ` [PATCH 3/6] kernel-fitimage: Use KERNEL_OUTPUT_DIR where appropriate Sean Anderson
2022-10-21 23:37 ` [PATCH 4/6] uboot-sign: Use bitbake variables directly Sean Anderson
2022-10-21 23:37 ` [PATCH 5/6] uboot-sign: Split off kernel-fitimage variables Sean Anderson
2022-10-21 23:37 ` [PATCH 6/6] u-boot: Rework signing to remove interdependencies Sean Anderson
     [not found]   ` <f8039bfc391404e83464c6894ce3ebf5496f1da1.camel@linuxfoundation.org>
2022-10-26 16:49     ` Sean Anderson
2022-10-26 17:00       ` Richard Purdie [this message]
2022-10-26 17:21         ` Sean Anderson
2022-10-28 15:09           ` Richard Purdie
2022-10-28 15:29             ` Sean Anderson
2022-10-28 15:37               ` Richard Purdie
2022-11-01 16:14                 ` Sean Anderson
2022-11-01 17:29                   ` Richard Purdie
2022-11-01 17:40                     ` Sean Anderson
2022-11-01 17:44                       ` Richard Purdie
2022-11-01 17:54                         ` Sean Anderson
2022-11-01 18:02                           ` [OE-core] " Alexander Kanavin
2022-11-01 18:29                             ` Sean Anderson
2022-11-01 18:40                               ` Alexander Kanavin
     [not found]                           ` <172387EDE52D4BA6.10252@lists.openembedded.org>
2022-11-01 18:24                             ` Alexander Kanavin
2022-11-09 23:07                           ` Alexandre Belloni
2022-11-10 15:19                             ` Sean Anderson
2022-11-01 21:01                       ` [OE-core] " Ross Burton

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=514b492351ff6be577b80881adbc6b508fc04071.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sean.anderson@seco.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 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.