| Summary: | [pyro-next] refkit fails | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Armin Kuster <akuster> |
| Component: | autobuilder | Assignee: | Joshua Lock <joshuagloe> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | Medium+ | CC: | infras.ab.watcher, Infras.watcher, joshuagloe, meta.mr.watcher, meta.watcher, pidge, todor.minchev |
| Version: | 2.3.2 | ||
| Target Milestone: | 2.3.2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | New (Never tested) |
| Verified: | Documentation change: | Don't know | |
| Deadline: | 2017-09-08 | ||
|
Description
Armin Kuster
2017-09-07 23:25:48 UTC
this is blocking a clean build and maybe the release of the next Pyro 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 (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. There's a bug in the AB logic somewhere, it shouldn't be trying to build refkit for pyro or older. 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) *** Bug 12020 has been marked as a duplicate of this bug. *** Fix implemented and deployed to both clusters. http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=e964af8033b4d1616eb04429a71466b1f2e50200 |