Bug 5294 - bitbake -m does not clear the environment correctly when using bitbake background server
Summary: bitbake -m does not clear the environment correctly when using bitbake backgr...
Status: VERIFIED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.5.1
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-09-30 12:48 UTC by Stoicescu Cornel
Modified: 2013-10-15 14:57 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stoicescu Cornel 2013-09-30 12:48:18 UTC 
1) get poky sources (1.5 +)
NOTE: The poky source should not have an already-made 'build' directory within
2) in a fresh shell session, source oe-init-build-env-memres
3) issue 'bitbake man' and cancel the build when tasks start executing

-- there should be no issues --

4) close the bitbake server by issuing command: 'bitbake -m'
5) go back to the main poky dorectory and this time source oe-init-build-env
6) issue 'bitbake man'

-notice "Connection refused" error. Seems bitbake is still looking for the background server. 

NOTE: Don't reuse this shell session for any further tests. Close it and continue testing in a new one as there might still be issues with this feature.
Comment 1 Richard Purdie 2013-10-04 13:44:07 UTC 
We can't clear the parent environment easily but we can have the init script unset BBSERVER. I've posted patches to do that, and clean up a few other startup issues.
Comment 3 Stoicescu Cornel 2013-10-15 14:57:34 UTC 
Verified in master:113398d2587fa507be710ade46bb90e284292975