Bug 7504 - Layer details page is not populated after your build the layer
Summary: Layer details page is not populated after your build the layer
Status: VERIFIED NOTABUG
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.9
Assignee: Michael Wood
QA Contact: Alexandru Roman
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-03-23 15:44 UTC by Belen Barros Pena
Modified: 2015-09-14 13:15 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2015-03-23 15:44:56 UTC
Steps to reproduce:

* With Toaster in build mode, create a project using the Local Yocto Project release
* Build something (e.g. core-image-minimal)
* Once the build finishes, click on the openembedded-core layer on the project page

The layer details page is still empty. I tried with an imported layer as well, just in case this was a problem only with the core layers, but the same happens: the layer details page for my imported layer is also empty after building it.
Comment 1 Michael Wood 2015-05-14 17:11:46 UTC
Hmm having difficulty testing this, the only way I can think it's possible is that if the information generated by the build for that layer isn't being stored. Are the targets provided by the layer available in any of the typeaheads for instance?
Comment 2 Belen Barros Pena 2015-05-15 12:14:47 UTC
yes, recipe and machine suggestions do appear in the typeaheads, but I suspect some magic matching to layer index information must be happening there. If the information in the typeaheads were coming only from the builds, we would not have suggestions for machines.
Comment 3 Belen Barros Pena 2015-09-10 14:36:13 UTC
so, the information from the build is populated, but on a separate layer entry. How we deal with that problem is a whole other issue. Setting this to 'not a bug'.
Comment 4 Alexandru Roman 2015-09-14 13:15:35 UTC
Verified