<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Since picking up Dizzy I have noticed </div><div><br></div><div>"... is tainted from a forced run"<br></div><div><br></div><div> log line appears to stick forever once I have forced a fetch or compile on a component. The change to bring this in is here:<br></div><div><br></div><div><a href="https://code.amazon.com/packages/Zeus-poky/commits/60c40e5db57da094ab5ecfadf8e07dc6251bec66">https://code.amazon.com/packages/Zeus-poky/commits/60c40e5db57da094ab5ecfadf8e07dc6251bec66</a> <br></div><div><br></div><div>It appears to me that the resultant taint file for a component, once made, never goes away. It only effectively forces a fetch or recompile once, but the file itself remains. So in effect, with the new log message, once I taint a task I will forever see this log message even though it does not appear to actually do anything.</div><div><br></div><div>In other words, from core image-minimal</div><div><br></div><div>$ bitbake zlib -f -c fetch</div><div>$ bitbake zlib</div><div><br></div><div>---> at this stage I see the log and I see all the dependent tasks of fetch rerun as expected.<br></div><div>WARNING: .../meta/recipes-core/<a href="http://zlib_1.2.8.bb">zlib_1.2.8.bb</a>.do_fetch is tainted from a forced run</div><div><br></div><div>---> but if I bitbake zlib again, zlib has already been built post the force fetch, so I dont see bitbake
actually rebuild anything. BUT I still get the warning message. The warning message fires based on the presence of the taint file and it is still there in he component folder within stamps. </div><div>$ bitbake zlib</div><div><br></div><div>WARNING: .../meta/recipes-core/<a href="http://zlib_1.2.8.bb">zlib_1.2.8.bb</a>.do_fetch is tainted from a forced run</div><div><br></div><div>Is there something I am missing here? It appears to be a misleading log message.</div><div><br></div><div>-Ezekiel<br></div><div><br></div></span></body></html>