All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Crowe <mac@mcrowe.com>
To: openembedded-core@lists.openembedded.org
Subject: package.tgz files not touched in sstate-cache
Date: Fri, 29 Jan 2016 15:47:48 +0000	[thread overview]
Message-ID: <20160129154748.GB19208@mcrowe.com> (raw)

We have a shared sstate-cache that is populated by us building nightly
images for various branches using Jenkins. This cache is pruned
periodically (with special care of the siginfo files since we don't have
80b3974081c4a8c604e23982a6db8fb32c616058 yet.)

Recently we went back to one of those branches that hadn't been changed for
a while and were surprised to find that Bitbake wanted to build loads of
packages from source.

It turned out that whilst the populate_sysroot.gz and package_ipk.tgz files
were still in the sstate-cache, the package.tgz tarball was not. This meant
that the whole package was built again in order to satisfy the build
dependencies of other packages that had changed.

I'm suspicious that this behaviour was introduced by the optimisation in
a0f584ac3d5a94dec121b684206ecd40c968f7fc so we hadn't seen it on older
branches.

Is there a way to cause the package.tgz file to be touched during these
nightly builds too? Or, is there a way to get hold of the complete set of
sstate files so they can be touched all in one go?

Thanks.

Mike.


             reply	other threads:[~2016-01-29 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 15:47 Mike Crowe [this message]
2016-01-29 17:42 ` package.tgz files not touched in sstate-cache Richard Purdie
2016-02-01 11:14   ` Mike Crowe
2016-02-01 15:54     ` Mike Crowe

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=20160129154748.GB19208@mcrowe.com \
    --to=mac@mcrowe.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.