Bug 2336 - Proxy sanity check message is getting burried
Summary: Proxy sanity check message is getting burried
Status: RESOLVED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 1.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.2.1
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard: Fix now in master and denzil branch
: 2337 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-04-18 18:45 UTC by Dave Stewart
Modified: 2012-06-14 12:36 UTC (History)
9 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Stewart 2012-04-18 18:45:55 UTC
Running the near-final Hob for v1.2 in the Build Appliance. There is a sanity check run by Hob to make sure there is network connectivity before starting to do any fetches. The error message pops up, but it's like the 8th line in a 9 line text box. I honestly thought that there was some bug which got triggered rather than my proxy being improperly set.

These error messages must be changed to put the significant message FIRST so that users can easily see what's up.
Comment 1 Shane Wang 2012-04-19 03:01:00 UTC
This is not a problem for Hob. It is in sanity check in the bitbake server.
Comment 2 Shane Wang 2012-04-19 03:04:47 UTC
*** Bug 2337 has been marked as a duplicate of this bug. ***
Comment 3 Saul Wold 2012-05-18 13:25:04 UTC
The real issue is that the dialog presented by Hob includes the full text from the sanity.bbclass bb.fatal() error message.  Some or all of that text is not approprite for the hob.

RP suggested that we could raise an exception and depending on hob or cmdline handle it with a dialog or bb.fatal() message
Comment 4 Paul Eggleton 2012-05-21 10:45:51 UTC
Unfortunately an exception is not going to help since it won't propagate outside of the event handler. A specific event type could work though.
Comment 6 Paul Eggleton 2012-06-14 12:36:53 UTC
Fixed in denzil branch revisions 5b3a0eac61d39ae37c44eb644f2debf7d99596af and 78a5471a29fca1c61d1fbfe164e0ad3b34f5e8d2. Additionally one of Joshua's commits b30a243f3f9133b62a4003bc28374b0f931e6c41 needed to be added to avoid too much conflict resolution.