How to debug dependency/setscene/sstate issues

How to debug dependency/setscene/sstate issues

[Vuille, Martin (Martin)]

[-- Attachment #1: Type: text/plain, Size: 729 bytes --]

I am using Poky daisy / Yocto 1.6.1

Occasionally, when building a custom image or SDK after changing
a package recipe or package content, I find that the do_rootfs task is not
executed for the image or the do_populate_sdk task is not executed
for the sdk.

There are custom classes, packages, packagegroups involved, so it is
possible, nay likely, that the problem is something I did or should've
done but didn't.

How to approach this problem?

Because the problem is intermittent, I usually won't realize there was
a problem until after bitbake is done and didn't build what I expected.
Is there a way to retrospectively review bitbake's decision-making?
Or do I need to run with -DDD all the time?

MV



[-- Attachment #2: Type: text/html, Size: 3152 bytes --]

Re: How to debug dependency/setscene/sstate issues

[Bob Cochran]

Won't Toaster give you the insight you seek?

I still need to ramp up on mastering it, but I was hoping it would help 
with this sort of thing.



On 11/01/2014 08:08 AM, Vuille, Martin (Martin) wrote:
> I am using Poky daisy / Yocto 1.6.1
>
> Occasionally, when building a custom image or SDK after changing
>
> a package recipe or package content, I find that the do_rootfs task is not
>
> executed for the image or the do_populate_sdk task is not executed
>
> for the sdk.
>
> There are custom classes, packages, packagegroups involved, so it is
>
> possible, nay likely, that the problem is something I did or should’ve
>
> done but didn’t.
>
> How to approach this problem?
>
> Because the problem is intermittent, I usually won’t realize there was
>
> a problem until after bitbake is done and didn’t build what I expected.
>
> Is there a way to retrospectively review bitbake’s decision-making?
>
> Or do I need to run with –DDD all the time?
>
> MV
>
>
>

Re: How to debug dependency/setscene/sstate issues

[Vuille, Martin (Martin)]

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of Bob Cochran
> Sent: November 01, 2014 9:08 AM
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] How to debug dependency/setscene/sstate issues
> 
> Won't Toaster give you the insight you seek?
> 
> I still need to ramp up on mastering it, but I was hoping it would help with
> this sort of thing.
> 

I'm still a Yocto newbie, so not familiar with Toaster.

Thanks for the tip, I'll see what it can do for me.

MV
 

Re: How to debug dependency/setscene/sstate issues

[Barros Pena, Belen]

On 01/11/2014 13:45, "Vuille, Martin (Martin)" <vmartin@avaya.com> wrote:

>> -----Original Message-----
>> From: yocto-bounces@yoctoproject.org [mailto:yocto-
>> bounces@yoctoproject.org] On Behalf Of Bob Cochran
>> Sent: November 01, 2014 9:08 AM
>> To: yocto@yoctoproject.org
>> Subject: Re: [yocto] How to debug dependency/setscene/sstate issues
>> 
>> Won't Toaster give you the insight you seek?
>> 
>> I still need to ramp up on mastering it, but I was hoping it would help
>>with
>> this sort of thing.
>> 
>
>I'm still a Yocto newbie, so not familiar with Toaster.
>
>Thanks for the tip, I'll see what it can do for me.

Hi Martin,

You probably found this already, but just in case. The instructions to set
up Toaster:

https://wiki.yoctoproject.org/wiki/Toaster

When you select a build, the 'Tasks' section in the left navigation will
tell you which tasks used shared state objects (tasks with outcome
'cached'), and which tasks didn't find a valid shared state object and
executed instead (tasks with cache attempt set to 'File not in cache'). If
you click on a task name, you will see which file the task looked for and
where. This might help debug your issue.

There is a video explaining the Tasks information in Toaster at

https://wiki.yoctoproject.org/wiki/images/a/a4/Toaster-manual-v5.webmhd.web
m

Cheers

Belén

>
>MV
> 
>
>-- 
>_______________________________________________
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto

Re: How to debug dependency/setscene/sstate issues

[Vuille, Martin (Martin)]

Hi Belén,

> -----Original Message-----
> From: Barros Pena, Belen [mailto:belen.barros.pena@intel.com]
> Sent: November 03, 2014 9:12 AM
> 
> Hi Martin,
> 
> You probably found this already, but just in case. The instructions to set up
> Toaster:
> 
> https://wiki.yoctoproject.org/wiki/Toaster
> 
> When you select a build, the 'Tasks' section in the left navigation will tell
> you which tasks used shared state objects (tasks with outcome 'cached'),
> and which tasks didn't find a valid shared state object and executed instead
> (tasks with cache attempt set to 'File not in cache'). If you click on a task
> name, you will see which file the task looked for and where. This might help
> debug your issue.
> 
> There is a video explaining the Tasks information in Toaster at
> 
> https://wiki.yoctoproject.org/wiki/images/a/a4/Toaster-manual-
> v5.webmhd.web
> m
> 

Thanks for the info. I am now using Toaster successfully.

MV