Bug 12175

Summary: [Test Case 946] View detailed configuration information for a build
Product: [Build System, Metadata & Runtime] Toaster Reporter: Victor Manuel Rodriguez Garcia <victor.manuelx.rodriguez.garcia>
Component: toasterAssignee: David Reyna <david.reyna>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: jessica.zhang, randy.macleod, stanciux.mihail
Version: 2.4   
Target Milestone: 2.4.3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
screenshot none

Description Victor Manuel Rodriguez Garcia 2017-10-03 22:14:08 UTC
Created attachment 4048 [details]
screenshot

STATUS: FAILED
BUILD: 2.4 M4: rc1-592c3449697ce39bf07864fafd7f0a61ca230561
ENVIRONMENT: Fedora 26
STEPS TO REPRODUCE: 1. Start with a default Yocto project (qemux86), start the Toaster, and build "bitbake core-image-minimal".
 
2. In Toaster, select the build, and select the "Configuration" link in the left sidebar.

3. Observe that the configuration page has 2 tabs:
- Summary
- BitBake variables
The Summary tab is the default tab.

4. At the page Summary, The column from Layer commit has a mini button that does nothing.

EXPECTED OUTCOME: NA
Comment 1 David Reyna 2017-10-03 22:19:52 UTC
There should be a list of layers here. I can see this error in at least on of my Toaster instance builds.
Comment 2 David Reyna 2017-10-06 04:05:07 UTC
It appears that this defect is a side effect of:
  #12194 - Toaster server lost "toaster.conf" environment, user settings lost

Specifically, I think it is a result of this missing from the build environment: INHERIT+="toaster buildhistory"

Once I added the patch to #12194 the layer list as appears as expected. I will do more confirmation testing and then close this as a duplicate.
Comment 3 Randy MacLeod 2018-04-05 08:12:00 UTC
David, 
The related defect: 
  #12194 - Toaster server lost "toaster.conf" environment, user settings lost
is resolved so can you re-test this defect?
Comment 4 David Reyna 2018-05-10 10:04:30 UTC
This has been fixed by previous patches.

One can observe the list of layers, but the "mini-button" pops-up the layer's commit ID.