All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH 1/2] siggen: Drop copy_unihashes function
Date: Sat, 8 Jun 2024 12:25:24 +0200	[thread overview]
Message-ID: <2024060810252435af9fa7@mail.local> (raw)
In-Reply-To: <28eec7ae10919151679dbaefb9db807c92b1f1cf.camel@linuxfoundation.org>

On 08/06/2024 11:18:48+0100, Richard Purdie wrote:
> On Sat, 2024-06-08 at 12:16 +0200, Alexandre Belloni wrote:
> > Hello Richard,
> > 
> > 
> > On 04/06/2024 15:28:02+0100, Richard Purdie wrote:
> > > The code in OE-Core using this has been replaced with something
> > > more fit
> > > for purpose. Drop these function calls as they were never a great
> > > idea in the
> > > first place and cause IO slowdown for runqueue needing to sync the
> > > cache.
> > > 
> > > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > ---
> > > �lib/bb/siggen.py | 6 ------
> > > �1 file changed, 6 deletions(-)
> > > 
> > > diff --git a/lib/bb/siggen.py b/lib/bb/siggen.py
> > > index 92066da00c..89b70fb6a4 100644
> > > --- a/lib/bb/siggen.py
> > > +++ b/lib/bb/siggen.py
> > > @@ -201,9 +201,6 @@ class SignatureGenerator(object):
> > > ���� def save_unitaskhashes(self):
> > > �������� return
> > > �
> > > -��� def copy_unitaskhashes(self, targetdir):
> > > -������� return
> > > -
> > > ���� def set_setscene_tasks(self, setscene_tasks):
> > > �������� return
> > > �
> > > @@ -418,9 +415,6 @@ class
> > > SignatureGeneratorBasic(SignatureGenerator):
> > > ���� def save_unitaskhashes(self):
> > > �������� self.unihash_cache.save(self.unitaskhashes)
> > > �
> > > -��� def copy_unitaskhashes(self, targetdir):
> > > -������� self.unihash_cache.copyfile(targetdir)
> > > -
> > 
> > It breaks sstatetests.SStateBundles.test_minimal_bundle which uses
> > copy_unitaskhashes
> 
> 
> Is that patch only in your -next branch? I didn't see this issue in my
> own testing which makes me wonder...

You are right, git blame told me it was applied a month ag and I didn't
check further. I'll drop the patch.



-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      parent reply	other threads:[~2024-06-08 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 14:28 [PATCH 1/2] siggen: Drop copy_unihashes function Richard Purdie
2024-06-04 14:28 ` [PATCH 2/2] runqueue: Avoid save_unitaskhashes Richard Purdie
2024-06-08 10:16 ` [bitbake-devel] [PATCH 1/2] siggen: Drop copy_unihashes function Alexandre Belloni
2024-06-08 10:18   ` Richard Purdie
2024-06-08 10:21     ` Alexander Kanavin
2024-06-08 10:25     ` Alexandre Belloni [this message]

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=2024060810252435af9fa7@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=bitbake-devel@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.