Bug 6169 - Toaster data collection fails due to lack of support for PROVIDES
Summary: Toaster data collection fails due to lack of support for PROVIDES
Status: RESOLVED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: All Multiple
: Medium normal
Target Milestone: 2.1
Assignee: Ed Bartosh
QA Contact:
URL:
Whiteboard: GUI design available
Depends on:
Blocks:
 
Reported: 2014-04-16 13:27 UTC by Paul Eggleton
Modified: 2016-01-12 17:59 UTC (History)
4 users (show)

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


Attachments
Design - Showing PROVIDES information (634.60 KB, application/pdf)
2015-05-18 15:29 UTC, Belen Barros Pena
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2014-04-16 13:27:57 UTC
Do a clean build of core-image-sato and break out of it after it has started running the first few tasks. (It's not mandatory to break out early but this just makes it easy to reproduce). If you wait for it to finish processing and then look in toaster_ui.log you'll see a traceback with a bunch of errors like this:

  stpd: KeyError saving recipe dependency for dmxproto, 'virtual/x86_64-poky-linux-gcc'

In store_dependency_information within buildinfohelper.py there is a check to see if the KeyError key starts with "virtual/", however the string value it's comparing it to has single quotes around it as seen above, which means that never works. Even when that is fixed though, there are other items being picked up that don't have the "virtual/" prefix, such as:

  stpd: KeyError saving recipe dependency for gconf-native, 'gobject-introspection-stub-native'

What this indicates is that there is currently no handling for PROVIDES satisfying DEPENDS, as opposed to a recipe with the same name. We'll probably need to change the model structure to handle this; additionally the code will need to understand that multiple recipes can satisfy a DEPENDS, and there may or may not be a PREFERRED_PROVIDER specifying which one should be selected. We should not try to duplicate the logic used within BitBake to determine which solution to use to satisfy DEPENDS - ideally we should read the output of that code so that we have a completely accurate picture of what is going on.
Comment 1 Belen Barros Pena 2015-04-30 15:47:15 UTC
The UI changes involved are:

1. In the recipe details page, include the provides information to show that a recipe satisfies virtual/recipe dependencies (e.g. kernel).

2. In the recipe details page, show 'satisfied by' information when a dependency on a virtual/recipe exists (e.g. oprofile)
Comment 2 Belen Barros Pena 2015-05-18 15:29:44 UTC
Created attachment 2516 [details]
Design - Showing PROVIDES information
Comment 3 Ed Bartosh 2015-12-07 12:36:53 UTC
Started to work on this.