Bug 12063 - [pyro-next] refkit fails
Summary: [pyro-next] refkit fails
Status: RESOLVED FIXED
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: 2.3.2
Hardware: x86 Multiple
: Medium+ critical
Target Milestone: 2.3.2
Deadline: 2017-09-08
Assignee: Joshua Lock
QA Contact:
URL:
Whiteboard:
: 12020 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-09-07 23:25 UTC by Armin Kuster
Modified: 2017-09-13 09:09 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: New (Never tested)
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-09-07 23:25:48 UTC
Please remove refkit from pyro and morty builds.
it failes for ERROR: ParseError in configuration INHERITs: Could not inherit file classes/distrooverrides.bbclass

that class does not exist in Pyro or morty.

PLEASE remove this layer from pyro and morty.
Comment 1 Armin Kuster 2017-09-07 23:26:25 UTC
this is blocking a clean build and maybe the release of the next Pyro
Comment 2 Joshua Lock 2017-09-11 16:43:28 UTC
The branch name format is incorrect, it is confusing but that's a decision the eclipse-poky team made long ago.

The format is eclipse-release-name/poky-release-name, except for the master branch.

Looking at a failed build:
https://autobuilder.yoctoproject.org/main/builders/eclipse-plugin-neon/builds/304

it looks like the correct format was used for the Mars Eclipse plugin but not the Neon Eclipse plugin:

branch_eclipse-poky-mars 	mars/pyro 	Trigger
branch_eclipse-poky-neon 	neon-pyro 	Trigger
Comment 3 Joshua Lock 2017-09-11 16:45:27 UTC
(In reply to comment #2)
> The branch name format is incorrect, it is confusing but that's a decision
> the eclipse-poky team made long ago.
> 
> The format is eclipse-release-name/poky-release-name, except for the master
> branch.
> 
> Looking at a failed build:
> https://autobuilder.yoctoproject.org/main/builders/eclipse-plugin-neon/
> builds/304
> 
> it looks like the correct format was used for the Mars Eclipse plugin but
> not the Neon Eclipse plugin:
> 
> branch_eclipse-poky-mars 	mars/pyro 	Trigger
> branch_eclipse-poky-neon 	neon-pyro 	Trigger

Commented on the wrong bug, apologies for the noise.
Comment 4 Joshua Lock 2017-09-11 16:46:26 UTC
There's a bug in the AB logic somewhere, it shouldn't be trying to build refkit for pyro or older.
Comment 5 Joshua Lock 2017-09-12 14:18:10 UTC
intel-iot-refkit only tracks oe-core master, so trying to build master of intel-iot-refkit with an older release is bound to fail at some point.

Rather than trying to keep on top of when intel-iot-refkit fails to build with releases we're going to switch the logic so that refkit images are only built for master and its pre-integration branches (master-next, ross/mut)
Comment 6 Joshua Lock 2017-09-12 14:18:48 UTC
*** Bug 12020 has been marked as a duplicate of this bug. ***
Comment 7 Joshua Lock 2017-09-13 09:09:05 UTC
Fix implemented and deployed to both clusters.

http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=e964af8033b4d1616eb04429a71466b1f2e50200