Bug 3620

Summary: bibake doesn't reparse the recipes after task dependency update in bbclass
Product: [Build System, Metadata & Runtime] BitBake Reporter: Muhammad Shakeel <email.mshakeel>
Component: bitbakeAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Medium CC: jessica.zhang, kergoth, poky.bs.watcher, poky.watcher
Version: unspecified   
Target Milestone: 1.4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Attachments:
Description Flags
test file to reproduce bug none

Description Muhammad Shakeel 2012-12-19 12:06:13 UTC
Created attachment 986 [details]
test file to reproduce bug

Steps to reproduce:

1) Download and place attached test.bbclass file in poky
2) Inherit test.bbclass in any recipe
3) Get the graph for that particular recipe i.e. $ bitbake -g <recipe>
4) You should see the following error:
ERROR: Task <yocto_dir>/poky/meta/recipes-extended/libaio/libaio_0.3.109.bb (do_test_task) has circular dependency on <yocto_dir>/poky/meta/recipes-extended/libaio/libaio_0.3.109.bb (do_fetch)

5) Replace line number 2 in test.bbclass with:
do_build[recrdeptask] += 'do_test_task'

6) Step number 5 will remove circular dependency for fetch task. Repeat Step 3. You will still see the same error <bug>. This is because bitbake didn't reparse the metadata.
6) Remove <build_dir>/tmp/cache/
7) Repeat step number 3. Now bitbake will reparse all the metadata and will not show any error.
Comment 1 Richard Purdie 2013-02-14 11:26:28 UTC
I just tried this with bitbake/poky master and the system reparsed things correctly after I changed test.bbclass. Which revision of the metadata did you find this issue with?
Comment 2 Richard Purdie 2013-02-15 12:39:39 UTC
If you can reproduce this against master, pleas reopen this. I'm going to assume this is with an older version of the metadata though, before some of the cache fixes.
Comment 3 Muhammad Shakeel 2013-02-22 07:46:43 UTC
I have also verified it against the master that it isn't reproducible. Seems like that it is resolved while fixing the cache issues, as Richard mentioned.