summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/cooker.py
diff options
context:
space:
mode:
authorElliot Smith <elliot.smith@intel.com>2016-02-10 18:34:10 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-02-11 22:34:19 +0000
commit1f7f07746629a55e4efd5f505e84eb6c66567115 (patch)
tree210b0ddd930a41666c0960ce15554d26fbf5f5d6 /bitbake/lib/bb/cooker.py
parent9a6cb10d4a611ed64700f9e9240c2958db7e2234 (diff)
downloadpoky-1f7f07746629a55e4efd5f505e84eb6c66567115.tar.gz
bitbake: buildinfohelper: unset brbe variable when build finishes
The brbe variable is set on the bitbake server when the Toaster UI starts. This enables Toaster to associate events with the correct build and build environment. However, the brbe variable is also used when a build starts to identify whether a new build needs to be created, or an existing one looked up. This causes a bug for command-line builds which happen after a Toaster-triggered build: because the brbe variable is never unset on the server or the buildinfohelper, the new command-line build events are treated as originating from the previous build. Ensure the brbe variable is reset when the buildinfohelper "closes" a build, so that each build then either sets the brbe variable (Toaster-triggered builds) or leaves it blank (command-line builds). Also modify the localhostbecontroller so that the brbe variable is not set on the server and not looked up from the server. This ensures that it is only set when the triggerBuild() method is called, and that it remains as None for command-line builds. [YOCTO #9021] (Bitbake rev: 4a6a8d0074f62208d843b06344be31ae73d9b745) Signed-off-by: Elliot Smith <elliot.smith@intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/cooker.py')
0 files changed, 0 insertions, 0 deletions