linux/poky.git/bitbake/lib/bb/server/process.py, branch dylan

bitbake: bitbake: Always use separate process for PR Service

2013-02-06T23:45:36+00:00

Using the threading module interacts badly with multiprocessing used elsewhere in bitbake under certain machine loads. This was leading to bitbake hanging on Ctrl+C when the PR Server was being used. This patch converts it to always use the daemonize code which then means the threading code isn't required. [YOCTO #3742] (Bitbake rev: 2d0bbd9398ab839bd2d1e29e50b25d52efb1ce2a) Signed-off-by: Richard Purdie

bitbake: server/process.py: Change timeout error handling

2012-11-21T09:22:22+00:00

In normal usage, we never hit the timeout issue. If we do, it becomes obvious that the current error handling is not good enough. The request may have made it to the server and the answer will get queued. This means the next command may get the return value from the previous command with suitably puzzling results. Without rewriting large sections of code, its not possible to avoid this problem. It is better to increase the timeout to several seconds giving the server a chance to respond and if it does timeout, hard exit since recovery is not possible with the code base today. I'd be happy to see the structure of this code improved but this quick fix at least stops corrupted builds from happening which has to be a good thing. (Bitbake rev: 410c11dd10736873f2dc587fbe9119c38831e693) Signed-off-by: Richard Purdie

bitbake: command: add error to return of runCommand

2012-11-01T11:46:22+00:00

Currently, command.py can return an error message from runCommand, due to being unable to run the command, yet few of our UIs (just hob) can handle it today. This can result in seeing a TypeError with traceback in certain rare circumstances. To resolve this, we need a clean way to get errors back from runCommand, without having to isinstance() the return value. This implements such a thing by making runCommand also return an error (or None if no error occurred). As runCommand now has a method of returning errors, we can also alter the getCmdLineAction bits such that the returned value is just the action, not an additional message. If a sync command wants to return an error, it raises CommandError(message), and the message will be passed to the caller appropriately. Example Usage: result, error = server.runCommand(...) if error: log.error('Unable to run command: %s' % error) return 1 (Bitbake rev: 717831b8315cb3904d9b590e633000bc897e8fb6) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

bitbake: bitbake/server: Remove dead console log code

2012-11-01T11:46:21+00:00

This code is dead and doesn't do anything so lets remove it. (Bitbake rev: 8d45739f49618757a5d7d79782deda355e3981ec) Signed-off-by: Richard Purdie

bitbake/process.py: Ensure queued UI events are queued right before we add our own handler

2011-07-07T09:57:43+00:00

(Bitbake rev: c7a9ef70ba91d47d53074e8d78cbc52f396144a7) Signed-off-by: Richard Purdie

process.py: Fix issue where early errors weren't making it to the console

2011-06-16T21:14:01+00:00

(Bitbake rev: d97f7d762e3d2f1b0da038d4d99f2531b2490670) Signed-off-by: Richard Purdie

make exception handling syntax consistent

2011-06-15T10:13:13+00:00

Update exception handling syntax to use the modern style: except ExcType as localvar (Bitbake rev: dbf5f42b06bef81749b13aa99945cc1292a6676d) Signed-off-by: Scott Garman Signed-off-by: Richard Purdie

bitbake/server/process: Implement getEvent()

2011-06-08T11:04:23+00:00

Signed-off-by: Richard Purdie

bitbake/server/process: Update to new server API

2011-06-08T10:38:47+00:00

Signed-off-by: Richard Purdie

bitbake: Add process server from upstream bitbake

2011-06-08T10:38:43+00:00

Signed-off-by: Richard Purdie