From: Martin Jansa <martin.jansa@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Why did my build need to redo so many tasks?
Date: Thu, 12 Feb 2015 23:19:46 +0100 [thread overview]
Message-ID: <20150212221946.GH2272@jama> (raw)
In-Reply-To: <54DD1A4C.60004@mlbassoc.com>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Thu, Feb 12, 2015 at 02:25:32PM -0700, Gary Thomas wrote:
> Yesterday, I built a large image using Poky/Yocto 870323cac1e
> Today I updated my Poky repo to 231d4a9d3
>
> When I rebuilt the same image, bitbake kicked off more than
> 5200 tasks, building virtually every package from scratch.
>
> How can I tell why this happened? I don't have buildhistory
> enabled, but I do still have the tmp & sstate-cache trees
> from the process. Is there enough info laying around that
> I can tell, e.g. why the GCC toolchain had to be rebuilt
> completely?
>
> Am I correct in assuming that bitbake-whatchanged is really
> a Quija board and can only tell me [in advance] what will need
> to be done if my layers change? When I ran it after the long
> build above, it didn't really tell me much :-(
I'm using
openembedded-core/scripts/sstate-diff-machines.sh
to create sstate signature snaphosts for interesting builds, then
when I'm surprised by number of re-executions, I create another snapshot
and compare them.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-02-12 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 21:25 Why did my build need to redo so many tasks? Gary Thomas
2015-02-12 21:33 ` Burton, Ross
2015-02-12 21:38 ` Gary Thomas
2015-02-12 22:19 ` Martin Jansa [this message]
2015-02-13 11:18 ` Barros Pena, Belen
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=20150212221946.GH2272@jama \
--to=martin.jansa@gmail.com \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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.