linux/poky.git/bitbake/lib/bb/ui/crumbs/hobeventhandler.py, branch 1.3.2

bitbake: hob: hob was freezing because it doesn't receives well the log file

2012-12-07T17:25:54+00:00

-after pressing "build image" button, hob was freezing because it didn't receive well the log file [YOCTO #3398] (Bitbake rev: e0bd4c4616511ec7918f801fb5e04984ebea8158) Signed-off-by: Cristiana Voicu Signed-off-by: Richard Purdie

bitbake: command: add error to return of runCommand

2012-12-07T17:25:54+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: d1002e33e05d45a7e1bd65d79537419a4057e43a) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

bitbake: hob/hobeventhandler: Describe the runCommand failure exception

2012-10-10T14:24:13+00:00

[YOCTO #1245] (Bitbake rev: 17f28f09452f70dfb67fce9a397a99deec84dfe5) Signed-off-by: Constantin Musca Signed-off-by: Richard Purdie

bitbake: hob/hobeventhandler: Throw an exception if runCommand fails

2012-10-10T14:21:40+00:00

- throw a Hob exception if runCommand returns 'Busy' or 'No such command' [YOCTO #1245] (Bitbake rev: 5a8e3baa66f845599a616f080a7efce81ecda631) Signed-off-by: Constantin Musca Signed-off-by: Richard Purdie

bitbake: Add sanity check progress screen

2012-09-27T15:45:26+00:00

This patch adds a sanity check progress screen to hob. The screen is displayed when Hob executes the sanity check procedure. The screen is displayed for at least 5 seconds. If a network error is detected, a special dialog is displayed which lets the user open the proxy configuration page directly. Note that currently bitbake triggers the network tests only when the value of its TMPDIR variable changes, which happens fairly rare on my system. This is the subject of another bug (#3026). Version 2 of the patch splits the changes in two parts (sanity.bbclass belongs to oe-core). [YOCTO #3025] (Bitbake rev: b48f1351271cc066ffe919db112b14834a6d8f8f) Signed-off-by: Bogdan Marinescu Signed-off-by: Richard Purdie

bitbake: hob/settings: implement a new tab in settings dialog to show SSTATE_MIRRORS

2012-09-27T15:45:25+00:00

Add a new tab to show correctly SSTATE_MIRRORS variable. Now you can add new mirrors or delete mirror. "info" image was also changed( it is smaller, so it can be next to labels). >From "Build environment" tab, SSTATE_DIR and SSTATE_MIRRORS vars were removed. [YOCTO #2893] (Bitbake rev: 1a81e27365d969e4ad4b4f0aec290aa967a8a35f) Signed-off-by: Cristiana Voicu Signed-off-by: Richard Purdie

bitbake: hob: don't show error dialog for errors during building

2012-09-24T11:13:50+00:00

During building we already report errors in a special tab and indicate when the build has failed; bringing up a dialog was a regression introduced in bitbake revision 5bab81b124087d63d6eb62a861e1241714fcd483. Fixes [YOCTO #3151]. (Bitbake rev: cf0a67d62f631aa48d1afc3fbdd0f73995b1c401) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: hob: report event handler failures

2012-09-20T10:48:39+00:00

If an event handler failed we were not recieving an error message - parsing just "froze" at 99%. This is because we were expecting a CommandFailure event and this never happened in the case of RequestPackageInfo which is where the failure was occurring. This also required tweaking the error formatting slightly, taking the return value of the format function rather than the message property since the latter only seems to contain the first line without the traceback in the case of event handler failure. Other error cases were tested and their message formatting is unaffected by this change. Final part of the fix for [YOCTO #2651]. (Bitbake rev: 5bab81b124087d63d6eb62a861e1241714fcd483) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: hob: format error messages properly

2012-09-14T08:50:33+00:00

Error messages that use arguments need to be formatted properly, or we don't get the full message. Use a formatter to do this when an error occurs. Partial fix for [YOCTO #2983]. (Bitbake rev: 6783538884adecd914909a9ab4ca73c27575f3ad) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: hob2: remove class hcc

2012-09-07T11:10:40+00:00

Because class hcc is useless, remove it. (Bitbake rev: 08d4a0f76542e05755c298b3875ea373e5512e13) Signed-off-by: Kang Kai Signed-off-by: Richard Purdie