public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Mike Crowe <mac@mcrowe.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] XZ_THREADS changing do_image_cpio task hash
Date: Wed, 11 Feb 2026 12:56:19 +0000	[thread overview]
Message-ID: <aYx8c9SIXh9q0LXF@mcrowe.com> (raw)
In-Reply-To: <CANNYZj_-3ZRL1-TTJKENbrkSE74951i5TxN=uJ1D-k3sL7mLKQ@mail.gmail.com>

On Wednesday 11 February 2026 at 12:41:30 +0100, Alexander Kanavin wrote:
> On Tue, 10 Feb 2026 at 17:28, Mike Crowe via lists.openembedded.org
> <mac=mcrowe.com@lists.openembedded.org> wrote:
> 
> > Am I missing an obvious reason why the task hash should change? Our build
> > hosts and developer machines have varying numbers of CPUs and this is
> > causing a lack of sstate sharing. :(
> 
> There might be a real issue in there somewhere but I need to point out
> that none of the image tasks contribute anything to sstate, so if you
> want to improve sstate reuse, images are the wrong place to start
> looking.

It's actually the kernel tasks that include the initramfs image that I'm
interested in getting from sstate.

In my testing, although the image is always rebuilt, the kernel does
successfully come from sstate when XZ_THREADS matches.

(There is also an ugly proliferation of separate siginfo files for the
various hashes in sstate, even if there are no actual artifacts, but these
are small.)

Thanks.

Mike.


      reply	other threads:[~2026-02-11 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 16:28 XZ_THREADS changing do_image_cpio task hash Mike Crowe
2026-02-11 11:41 ` [OE-core] " Alexander Kanavin
2026-02-11 12:56   ` Mike Crowe [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=aYx8c9SIXh9q0LXF@mcrowe.com \
    --to=mac@mcrowe.com \
    --cc=alex.kanavin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox