| Summary: | Extensible SDK: SDK installation ERROR: Unexpected tasks left over to be executed | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu> | ||||||
| Component: | devtools / tool chain | Assignee: | Paul Eggleton <bluelightning> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Francisco Pedraza <francisco.j.pedraza.gonzalez> | ||||||
| Severity: | normal | ||||||||
| Priority: | Medium+ | CC: | jose.perez.carranza, meta.mr.watcher, meta.watcher | ||||||
| Version: | 2.1 | ||||||||
| Target Milestone: | 2.2 M3 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | Don't know | |||||||
| Attachments: |
|
||||||||
|
Description
Bogdan Alexandru Voiculescu
2016-02-09 15:26:37 UTC
I think it is a configuration mistake; I can reproduce it if I add manually an auto.conf file in conf directory. Still without this file it installs fine. I will investigate more on this (I will create an AB job with a task populate_sdk_ext). That is bizarre - what are you putting in this auto.conf file? This is the content.
# WARNING: this configuration has been automatically generated and in
# most cases should not be edited. If you need more flexibility than
# this configuration provides, it is strongly suggested that you set
# up a proper instance of the full build system and use that instead.
INHERIT += "report-error"
DISTRO = "poky"
PACKAGE_CLASSES = "package_rpm package_deb package_ipk"
SDKMACHINE ?= "x86_64"
IMAGE_FSTYPES_append = " tar.gz"
BB_TASK_NICE_LEVEL = "5"
BB_TASK_NICE_LEVEL_task-testimage = "0"
BB_TASK_IONICE_LEVEL = "2.7"
BB_TASK_IONICE_LEVEL_task-testimage = "2.1"
DL_DIR ?= "${TOPDIR}/downloads"
INHERIT += "own-mirrors"
SOURCE_MIRROR_URL = "file:////media/sstate/downloads"
SRCREV_pn-build-appliance-image = "${AUTOREV}"
MACHINE = "qemux86"
PREMIRRORS = ""
ADTREPO = "http://adtrepo.yoctoproject.org//2.0+snapshot"
I just tried with your auto.conf file and I cannot reproduce the issue with master. Also, you said "beaglebone" and yet it clearly has MACHINE = "qemux86" in the auto.conf file you pasted - I guess that's being overridden by the local.conf file you're using? Can you attach that file? Created attachment 2984 [details]
conf auto file
Created attachment 2985 [details]
local conf
So MACHINE is going to be "qemuarm" with the files you just posted, not "beaglebone" - since auto.conf is parsed first, and in local.conf you are setting MACHINE with ?= which will do nothing since a value is already set. I also still can't reproduce this even with the new configuration. So I created a core-image-minimal with beaglebone and when I ran populate_sdk_ext took the qemuarm value and things broken? No, that in and of itself wouldn't break things, and in any event I had that configuration here and the problem didn't occur, so something else is causing it. So I think we've established offline to the extent possible that this was a result of a shared sstate directory where the dbus sstate artifacts were removed by another user (possibly with bitbake -c cleansstate dbus), but the task was still stamped within the build of the SDK; gen-lockedsigs-cache doesn't error if an sstate archive is missing because at the moment it can't tell the difference between an sstate task where the archive should be present and a non-sstate task where it's expected that it won't. The question is where does that leave us with this bug? Moving to 2.2 - I think the only thing we can really do here is to have this error happen earlier, which means testing at build time that the SDK will be able to install properly. I've added extra checks to detect this early with a better error message. |