Skip to contentSkip to conversation

Why did my build need to redo so many tasks?

DISCUSSION Gary Thomas 4 participants 5 messages Feb 12, 2015 – Feb 13, 2015

lore
Share & tools
lore
#0 lore raw

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 :-(

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 12 lines · Gary Thomas

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?

Quoted 5 lines

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 :-(

If you checkout the first commit, do a build, then the second commit and run bitbake-whatchanged, it should tell you the difference.

Looking at the git log shows cc5f80, which is a change to libtool, so everything inheriting autotools will need a rebuild.

Ross

#2 lore raw
Quoted 21 lines · Ross

On 12 February 2015 at 21:25, Gary Thomas <[email protected] <mailto:[email protected]>> 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 :-(

Quoted 3 lines

If you checkout the first commit, do a build, then the second commit and run bitbake-whatchanged, it should tell you the difference.

Looking at the git log shows cc5f80, which is a change to libtool, so everything inheriting autotools will need a rebuild.

Ouch, thanks. Next time I'll know a bit more on how to diagnose this.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#3 lore raw
In reply to Gary Thomas
Quoted 12 lines · Gary Thomas

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?

Quoted 4 lines

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.

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#4 lore raw
Quoted 18 lines · Martin Jansa
Quoted 12 lines · Gary Thomas

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?

Quoted 4 lines

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 :-(

Quoted 5 lines

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.

And there is Toaster, which also reports on sstate use, although after the build is done and it might not give you the same granularity as the other suggestions. It looks nice, though ;)

Belén

Quoted 3 lines
Signature · 2 lines
-- 
Martin 'JaMa' Jansa     jabber: [email protected]