Bug 5535 - bitbake server must soft-reset between builds
Summary: bitbake server must soft-reset between builds
Status: VERIFIED WONTFIX
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.6
Hardware: All Multiple
: Medium+ major
Target Milestone: 1.6 M4
Assignee: Cristiana Voicu
QA Contact:
URL:
Whiteboard:
: 5293 (view as bug list)
Depends on: 5603
Blocks: 5187
  Show dependency tree
 
Reported: 2013-11-14 12:31 UTC by Alexandru Damian
Modified: 2014-07-31 14:13 UTC (History)
8 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Damian 2013-11-14 12:31:35 UTC
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.
Comment 1 Cristiana Voicu 2013-11-21 10:35:53 UTC
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
Comment 2 Cristiana Voicu 2013-11-25 14:35:56 UTC
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.
Comment 3 Cristiana Voicu 2013-11-25 14:36:45 UTC
*** Bug 5293 has been marked as a duplicate of this bug. ***
Comment 4 Cristiana Voicu 2014-04-02 13:43:28 UTC
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.
Comment 5 Alexandru Georgescu 2014-07-31 14:13:05 UTC
verified as per above comments.