Bug 5493 - Toaster must be able to stop a bitbake server, and clean all artifacts
Summary: Toaster must be able to stop a bitbake server, and clean all artifacts
Status: VERIFIED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 1.7 M1
Assignee: Alexandru Damian
QA Contact: Mihail Stanciu
URL:
Whiteboard: TC done
Depends on:
Blocks: 5595
  Show dependency tree
 
Reported: 2013-11-06 16:17 UTC by Alexandru Damian
Modified: 2014-08-07 12:00 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

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 Alexandru Damian 2013-11-06 16:17:52 UTC 
As a user, I want, after using Toaster to start a Bitbake server, and shutting down the Bitbake server through Toaster, to have a clean environment devoid of Bitbake build artifacts.
Comment 1 Alexandru Damian 2014-06-13 13:31:01 UTC 
The bitbake server is automatically stopped at build completion by toaster, if managed mode is detected.

Merged in origin/master.
Comment 2 Alexandru Damian 2014-07-30 09:16:11 UTC 
to see that the bitbake server process is running, look for:

python /home/ddalex/ssd/yocto/poky/bitbake/bin/bitbake --postread conf/toaster.conf --server-only -t xmlrpc -B localhost:8200


to test the clean functionality, please verify that the bitbake server and all associated processes are stopped

the clean artefacts policy is not yet defined, and not implemented
Comment 3 Mihail Stanciu 2014-08-07 11:20:44 UTC 
Verified on master: 2d1660112e54653f7bb763939d0416472c49fe01
Test case 1041 created.