Bug 11823 - AB: test intel-iot-refkit with the right submodules
Summary: AB: test intel-iot-refkit with the right submodules
Status: RESOLVED DUPLICATE of bug 11745
Alias: None
Product: IoT Reference OS Kit
Classification: Yocto Project Subprojects
Component: intel-iot-refkit-default (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.4 M2
Assignee: Stephano Cetola
QA Contact: yeoh ee peng
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-07-24 04:06 UTC by Armin Kuster
Modified: 2017-07-25 15:22 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Armin Kuster 2017-07-24 04:06:52 UTC
builddir : /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-refkit
buildername : nightly-refkit
buildnumber : 74
commit-description : 2.4_M1-574-g2ec7562

error messages:

Last 60 lines of "BuildImages.stdio" Error log:

ERROR: Layer 'refkit' depends on layer 'iot-web', but this layer is not enabled in your configuration
ERROR: Layer 'refkit-gateway' depends on layer 'iot-web', but this layer is not enabled in your configuration
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
Detailed log of last build step: https://autobuilder.yocto.io/builders/nightly-refkit/builds/74/steps/BuildImages_1/logs/stdio
Last 60 lines of "BuildImages_1.stdio" Error log:

ERROR: Layer 'refkit' depends on layer 'iot-web', but this layer is not enabled in your configuration
ERROR: Layer 'refkit-gateway' depends on layer 'iot-web', but this layer is not enabled in your configuration
ERROR: Layer 'security' depends on layer 'xfce-layer', but this layer is not enabled in your configuration
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
Comment 1 Stephano Cetola 2017-07-25 14:31:39 UTC
I'm currently adding functionality to autobuilder which should fix these issues.
Comment 2 Patrick Ohly 2017-07-25 14:58:12 UTC
meta-refkit/conf/bblayers.conf.sample contains ##OEROOT##/../iot-web-layers/meta-iot-web. However, upstream meta-iot-web recently renamed the collection.

This should be addressed by 
https://github.com/intel/intel-iot-refkit/pull/253/commits/a543d6c0a2df1c07714d99c584f70ddfaf54727c which is in intel-iot-refkit master.
Comment 3 Patrick Ohly 2017-07-25 15:02:06 UTC
(In reply to comment #1)
> I'm currently adding functionality to autobuilder which should fix these
> issues.

What do you intend to add?

Was the problem that the AB checked out iot-web-layers master instead of the revision that intel-iot-refkit specified?
Comment 4 Patrick Ohly 2017-07-25 15:06:09 UTC
(In reply to comment #3)
> Was the problem that the AB checked out iot-web-layers master instead of the
> revision that intel-iot-refkit specified?

What it should do is check out exactly the revisions specified by intel-iot-refkit (see meta-refkit/README.rst for a hint if you need to do it in a script, or use "git submodules"), then update bitbake and OE-core to master or master-next (depending on what the AB is currently testing).
Comment 5 Stephano Cetola 2017-07-25 15:08:31 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > Was the problem that the AB checked out iot-web-layers master instead of the
> > revision that intel-iot-refkit specified?
> 
> What it should do is check out exactly the revisions specified by
> intel-iot-refkit (see meta-refkit/README.rst for a hint if you need to do it
> in a script, or use "git submodules"), then update bitbake and OE-core to
> master or master-next (depending on what the AB is currently testing).

That is exactly the path I'll be taking. The problem I'm correcting is how the autobuilder currently finds those git submodules.

Today, it is hard-coded like this:

CreateBBLayersConf:
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/tree/buildset-config.controller/nightly-refkit.conf

Obviously, this is a terrible idea. I'll be removing the need for this.
Comment 6 Stephano Cetola 2017-07-25 15:22:29 UTC
Closing as a duplicate of 11745.

*** This bug has been marked as a duplicate of bug 11745 ***