Created attachment 4417 [details] BUG2_RECIPE Following are the test cases 1113,1400,1401 1)Environmental setup: Branch: Master Build name: yocto-2.7_M1.rc1 poky commit: fe43e599327f26b399c1883205e988236a5e51bd 2)Expected behavior: Recipes" table and "machines" table are should populated in imported layer as well as Machine table should display after clicking Machines Tab on project page 3)Actual behavior: "Recipes" table and "machines" table are not getting populated inside imported layer and Machine table are not getting displayed after clicking Machines Tab on project page 4)Regression result with previous builds: 2.5.2.rc1, Poky commit : 95ebfb33e4c0aa9669f318e061a4d7540b84f4ac 5)Screen shot: Attached in mail with name "BUG2_RECIPE.png" , BUG2_MACHINE.png and BUG2_PROJECT_MACHINE.png 6)Logs, if any:->N/A 7)Workaround if any:->N/A
Created attachment 4418 [details] BUG2_MACHINE
Created attachment 4419 [details] BUG2_PROJECT_MACHINE
There are two issues here. 1) Toaster > Plan 110 > Case 1112 The sample layer has changed since the test case 1112 was written. There is for example no longer a directory "meta-acer". UPDATED: (the "->" indicated the changed content) 3. Check that the import layer form is shown, with the following elements as text fields to be filled out: Layer name (example: meta-imported) Git repository URL (example: git://github.com/shr-distribution/meta-smartphone.git) -> Repository subdirectory (optional) (example: meta-motorola) Revision (example: master) -> 4. In the "Layer dependencies" section, add "meta-android" if not already present in this project. Toaster will also discover and add its dependent layer "meta-oe". The imported layer was failing silently with the obsolete subdirectory, so that needs to be fixed. 2) Toaster > Plan 110 > Case 1113 This needs a step added. When you import a layer and look at its recipe and machine content, it will be empty with the message "Toaster learns about layers when you build them. If this layer provides any recipes, they will be listed here after you build the meta-imported layer." To build the layer, one needs to: (a) Set the machine to for example "athene" (b) Build an applicable image like "android-system-image-athene" (note that core-image-base fails) This has been a chicken and egg situation, since user needs information about the layer before they can build it to get information about it (presumably from the same place that the user learned about the layer). I implemented a import layer look-ahead for local layers the was able to preset some of this information, and I should do the same for remote layers (which will require a forced clone and then the layer tree analysis). 3) I did complete a working build as per the above. I did not see any new layer information. I will investigate this further.