Bug 3496 - The Issues tab displays a badge, but no information on the issues
Summary: The Issues tab displays a badge, but no information on the issues
Status: VERIFIED FIXED
Alias: None
Product: Hob
Classification: Build System, Metadata & Runtime
Component: hob (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.4.2
Assignee: valentin
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-11-27 12:12 UTC by Belen Barros Pena
Modified: 2013-11-25 13:21 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
empty-issues-tab.png (27.86 KB, image/png)
2012-11-27 12:12 UTC, Belen Barros Pena 		no flags Details
empty-issues-info (100.12 KB, image/png)
2013-08-26 13:08 UTC, Andreea Brandusa Proca 		no flags Details
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 Belen Barros Pena 2012-11-27 12:12:49 UTC 
Created attachment 952 [details]
empty-issues-tab.png

While building core-image-minimal a badge came up in the Issues tab, but when I selected the tab to find out more about the issue, the tab was blank (see empty-issues-tab.png). I could not see any warnings or errors in the Log tab either.
Comment 1 Andreea Brandusa Proca 2013-03-14 07:45:47 UTC 
I can not reproduce it, so I set it to verified in master : 4da406cd50cf02a63ed76810a670aba1eb561c79.
Comment 2 Andreea Brandusa Proca 2013-08-26 13:08:57 UTC 
Created attachment 1441 [details]
empty-issues-info
Comment 3 Andreea Brandusa Proca 2013-08-26 13:09:59 UTC 
I get the error described by Belen on dylan:d734ab491a30078d43dee5440c03acce2d251425.
Comment 4 Cristiana Voicu 2013-09-30 08:51:03 UTC 
I spoke with Andreea, And she told me that she saw this error on master too. I didn't reproduce it yet, but I will investigate the code.
Comment 5 valentin 2013-11-20 16:48:59 UTC 
Hi Belen, 

Terms: errors and warnings are considered 'Issues' 

There are two ways to solve this:
    1: Consider errors to be the only 'Issues' (on error the build fails, hobs stops building and we can show the issues)
    2: Show both the warnings and errors, but for some warnings (e.g. "couldn't fetch, trying MIRRORS...") might determine the user to think that a package wasn't installed.

Which do you prefer?
Comment 6 Belen Barros Pena 2013-11-20 17:00:08 UTC 
(In reply to comment #5)
> Hi Belen, 
> 
> Terms: errors and warnings are considered 'Issues' 

Yes

> 
> There are two ways to solve this:
>     1: Consider errors to be the only 'Issues' (on error the build fails,
> hobs stops building and we can show the issues)
>     2: Show both the warnings and errors, 

This was the initial idea: making sure that any messages thrown by the build system were collected together in a single place for easy access. I still think this is a good thing to do. Errors should be displayed first, warnings afterwards.

but for some warnings (e.g.
> "couldn't fetch, trying MIRRORS...") might determine the user to think that
> a package wasn't installed.

Maybe, but that might have more to do with the content of the warning, and not so much with where it displays. 

> 
> Which do you prefer?

2! :)
Comment 8 Andreea Brandusa Proca 2013-11-25 13:21:27 UTC 
Verified in master:6ddb9bf0976169fde7eee16d70a83210aa354416.