Bug 3919

Summary: Forced rebuilds are ignored for subsequent builds
Product: [Build System, Metadata & Runtime] BitBake Reporter: Paul Eggleton <bluelightning>
Component: bitbakeAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Undecided CC: dvhart, poky.bs.watcher, poky.watcher, ross.burton
Version: 1.3   
Target Milestone: ---   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Paul Eggleton 2013-02-21 14:24:59 UTC 
If you use the -f or -C options to force the re-execution of a task, the next time bitbake runs the old version of the task's output will be restored from shared state. The cause of this is the stamp deletion process at the end of running a task also deletes the taint file that we use to alter the task signature, so next time the task is called for it has the old value without the taint.

This also affects kernel menuconfig since that taints the do_compile task when it finishes.
Comment 1 Paul Eggleton 2013-02-21 15:50:35 UTC 
Patch sent for review:

http://lists.linuxtogo.org/pipermail/bitbake-devel/2013-February/004171.html
Comment 2 Darren Hart 2013-02-25 17:12:40 UTC 
I think I'm hitting this on Danny as well.
Comment 3 Ross Burton 2013-02-25 17:14:33 UTC 
Yep, I intend to encourage this to be merged to the 1.16 branch for danny.
Comment 4 Darren Hart 2013-02-25 17:15:43 UTC 
Merged to master:

commit 406cb9920fad57a23d2139f657c41598eb5087bf
Author: Paul Eggleton <paul.eggleton@linux.intel.com>
Date:   Thu Feb 21 15:23:35 2013 +0000

    bitbake: build.py: avoid deleting taint files when writing stamps