Bug 2600 - bitbake -p does not save cache properly
Summary: bitbake -p does not save cache properly
Status: VERIFIED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.2
Hardware: All Multiple
: Medium normal
Target Milestone: 1.3 M3
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard: (p1)(fixed)
Depends on:
Blocks:
 
Reported: 2012-06-13 12:54 UTC by Paul Eggleton
Modified: 2012-09-03 14:05 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2012-06-13 12:54:41 UTC 
If you clear the cache (or do touch conf/local.conf) then do "bitbake -p", bitbake parses all recipes. However if you then run bitbake to actually build something (say, quilt-native), it re-runs the parse. This suggests that the parse done by "bitbake -p" is not being properly saved, and is a regression since this used to work fine.
Comment 1 Paul Eggleton 2012-06-25 16:35:59 UTC 
This turned out to be caused by a couple of variables changing between executing bitbake directly (as is the case with -p) and wrapping bitbake in pseudo (as happens when you actually request bitbake to build something). These variables which were creeping into the environment and changing the data hash, which effectively invalidates the parser cache.
Comment 2 Paul Eggleton 2012-06-25 16:36:23 UTC 
Fixes merged to master in revisions d0c615e51e57435034ffba5e55a17fae833c6688 and bd3fd17fc57f4091308c3326c6ae29020e374da8.
Comment 3 Alexandru Georgescu 2012-09-03 14:05:03 UTC 
Marked as Verified.