Bitbake, in server mode, retains time/date related variable values between builds. This may lead to conflicts for build artifacts that use time-related identifiers. Bitbake must soft-reset time-related variables at build start and force re-evaluation of all dependent variable fields.
I have some questions related to this issue: 1. What does it means "soft"? 2. Should it reset all the variables, or only those specific to time/date? I saw that CONSOLE_LOG is not using BUILDNAME # Complete output from bitbake BB_CONSOLELOG ?= "${LOG_DIR}/cooker/${MACHINE}/${DATETIME}.log" self.data.setVar("BUILDNAME", time.strftime('%Y%m%d%H%M%S')) The simpliest idea is to define each time those vars (e.g. using "=" instead of "?=") Or, should this happen for all the variables? Thanks, Cristiana
The purpose for this bug is to reparse the configuration between builds when using a bitbake server. I will mark 5293 as duplicate, because it has the same objective.
*** Bug 5293 has been marked as a duplicate of this bug. ***
After a metting regarding memres, we've decided that the reset will happen only if it is trigered by a client. This issue is addressed in bug #5603, so I will close this bug.
verified as per above comments.