| Summary: | The Issues tab displays a badge, but no information on the issues | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Hob | Reporter: | Belen Barros Pena <belen.barros.pena> | ||||||
| Component: | hob | Assignee: | valentin <valentin.popa> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Medium | CC: | andreea.b.proca, cristian.iorga, cristiana.voicu, jessica.zhang, poky.bs.watcher, poky.watcher, valentin.popa | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 1.4.2 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||
| Attachments: |
|
||||||||
I can not reproduce it, so I set it to verified in master : 4da406cd50cf02a63ed76810a670aba1eb561c79. Created attachment 1441 [details]
empty-issues-info
I get the error described by Belen on dylan:d734ab491a30078d43dee5440c03acce2d251425. 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. 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?
(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! :) Patch merged: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=300b6f7f49857d5e6a86610003a7753a2f1daed6 Verified in master:6ddb9bf0976169fde7eee16d70a83210aa354416. |
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.