linux/poky.git/bitbake/lib/bb/runqueue.py, branch 1.2_M4.rc3.1

runqueue: wait and deal with those sub-processes as soon as they are os.killed() when "Force stop"

2012-03-30T16:20:21+00:00

When "Force stop" is performed during the build stage, after os.kill() kills the build sub-processes, there are many python processes in the system. In Hob, when the user initiates a new build, os.waitpid() in runqueue_process_waitpid() will be called, and the pids of those processes will be returned as result[0], then self.build_pids[result[0]] will throw KeyError exception because now for the new build self.build_pids is empty. This patch is to address the above issue to collect the results and handle the sub-processes as soon as they are killed. [Yocto #2186] (Bitbake rev: e9f4ca467e795bbc520d12b0e7a5985b6ff0a20e) Signed-off-by: Shane Wang Signed-off-by: Richard Purdie

Typo: "nonexistant" -> "non-existent"

2012-03-20T15:21:32+00:00

(Bitbake rev: c4c8df0e1e77f99f3ee0b07e1748116fc362819f) Signed-off-by: Robert P. J. Day Signed-off-by: Richard Purdie

runqueue.py: When checking whether stamps are valid for setscene, recurse

2012-03-16T10:51:17+00:00

Currently the code checking whether stamps are valid only traverses one step of the dependency graph. This works fine in the normal cases where we've already validated dependencies but for the setscene code, it doesn't work well. A typical problem usecase is something like: bitbake gcc-cross -c unpack -f bitbake gcc-cross which will ignore any sstate files already cached which could be used to speed up the gcc-cross build. This becomes particularly problematic with multiple gcc builds where only one should rebuild yet they all do. This patch teaches the stamp code to be able to recurse within a given fn which gives the behaviour people would expect from the code and allows bitbake to make better use of prebuild sstate objects. (Bitbake rev: e68814cb2e8da523d4ddf05e8ceddfaa19244851) Signed-off-by: Richard Purdie

meta/classes: Convert to use appendVar and appendVarFlags

2012-03-05T18:36:53+00:00

(From OE-Core rev: 3b57de68e70e77dbc03c0616a83a29a2e99e40b4) Signed-off-by: Richard Purdie

bitbake/runqueue: fix python error on scenequeue task failure

2012-03-01T15:51:36+00:00

Fixes a regression introduced in commit e8a3499c95a6d4f2b8fed002fb9504733c5be3c6 which resulted in a backtrace on setscene task failure due to trying to dereference the setscene task ID twice. (Bitbake rev: 8b846a92a58b5c20d7cfd2efd32b763e95c3c2fd) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

runqueue.py: initialize rqexe at RunQueue's init function

2012-03-01T15:51:36+00:00

Sometimes user stops the build before runqueue is established, for example, at the stage of running add_unresolved() function. This will cause RunQueue to use rqexe field in finish_runqeue() before initialized. This will cause endless print of "Running idle function" if use process server. This commit initialize rqexe variable in RunQueue's init function, and add a judgement in finish_runqueue(). (Bitbake rev: 59f817723172092a87738c79f555e605f55ea375) Signed-off-by: Dongxiao Xu Signed-off-by: Richard Purdie

bitbake: fix setscene task start/failure handling

2012-02-28T12:27:22+00:00

* When a setscene task starts, print out that it's starting in the UI (ensuring we get the correct task name) * When a setscene task fails, ensure we remove it from the list of running tasks so that if you break out any time afterwards it is not still listed. (Bitbake rev: e8a3499c95a6d4f2b8fed002fb9504733c5be3c6) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake/runqueue: make dry-run do everything except execute

2012-02-28T12:27:21+00:00

Make dry-run do everything except executing the task, instead of cutting it off earlier. This fully tests the code path for running the child task (parsing and fakeroot), as well as enabling future functionality such as using dry-run to produce signature files. (Bitbake rev: bf1d7739618dabf3872a868230c0112b9ad2a2c0) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

V5 Disk space monitoring

2012-02-26T11:05:27+00:00

Monitor disk availability and take action when the free disk space or amount of free inode is running low, it is enabled when BB_DISKMON_DIRS is set. * Variable meanings(from meta-yocto/conf/local.conf.sample): # Set the directories to monitor for disk usage, if more than one # directories are mounted in the same device, then only one directory # would be monitored since the monitor is based on the device. # The format is: # "action,directory,minimum_space,minimum_free_inode" # # The "action" must be set and should be one of: # ABORT: Immediately abort # STOPTASKS: The new tasks can't be executed any more, will stop the build # when the running tasks have been done. # WARN: show warnings (see BB_DISKMON_WARNINTERVAL for more information) # # The "directory" must be set, any directory is OK. # # Either "minimum_space" or "minimum_free_inode" (or both of them) # should be set, otherwise the monitor would not be enabled, # the unit can be G, M, K or none, but do NOT use GB, MB or KB # (B is not needed). #BB_DISKMON_DIRS = "STOPTASKS,${TMPDIR},1G,100K WARN,${SSTATE_DIR},1G,100K" # # Set disk space and inode interval (only works when the action is "WARN", # the unit can be G, M, or K, but do NOT use the GB, MB or KB # (B is not needed), the format is: # "disk_space_interval, disk_inode_interval", the default value is # "50M,5K" which means that it would warn when the free space is # lower than the minimum space(or inode), and would repeat the action # when the disk space reduces 50M (or the amount of inode reduces 5k) # again. #BB_DISKMON_WARNINTERVAL = "50M,5K" [YOCTO #1589] (Bitbake rev: 4d173d441d2beb8e6492b6b1842682f8cf32e6cc) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake/runqueue: Ensure finish_now() sets the runqueue state consistently

2012-02-26T11:04:38+00:00

If we call finish_now(True), rq.state is not updated to match. This makes the behaviour of finish_now(False) and finish_now(True) consistent so both leave rq.state consistently. (Bitbake rev: 9079ae0ab74f9232b7e9853b2013b051d4fcf623) Signed-off-by: Richard Purdie