| Summary: | [meta-mingw] nativesdk-mingw-w64-runtime_3.1.0.bb fails in do_compile on the AB | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Other YP Layers | Reporter: | Joshua Lock <joshuagloe> | ||||
| Component: | layers | Assignee: | Juro Bystricky <juro.bystricky> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium+ | CC: | poky.bs.watcher, poky.watcher | ||||
| Version: | 2.3 | ||||||
| Target Milestone: | 2.3 M4 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Joshua Lock
2017-03-02 10:52:14 UTC
I just did a fresh pull of poky/master and meta-zephyr. With local.conf: SDKMACHINE ?= "i686-mingw32" I got a clean build: Build Configuration: BB_VERSION = "1.33.2" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "ubuntu-14.04" TARGET_SYS = "i586-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "2.2+snapshot-20170302" TUNE_FEATURES = "m32 i586" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "master:ea2fd77ba5c5482dac4682381d82a76cc30391fa" meta-mingw = "master:2a3ae35de9c846354a07ac1a2db51382cd290c02" Initialising tasks: 100% |###############################################################################################################################################################| Time: 0:00:02 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Tasks Summary: Attempted 1973 tasks of which 10 didn't need to be rerun and all succeeded. Can you please provide more info regarding the failed build so I can try to reproduce it? Created attachment 3641 [details] compilation log Apologies, I meant to add more info and got distracted. Build was on debian-testing, you can see output here: https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/170/steps/BuildImages_3/logs/stdio Compilation log attached. I have a tarball of the full nativesdk-mingw-w64-runtime directory from the failed build if there's anything else you would like me to provide. Well, I repeated the build (using a Ubuntu 14 container), with settings same as those that failed on AB: Build Configuration: BB_VERSION = "1.33.2" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "ubuntu-14.04" TARGET_SYS = "i586-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "2.2+snapshot-20170302" TUNE_FEATURES = "m32 i586" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "HEAD:9e9b7d1f4eb05548c5347717362431db386bc8dc" meta-mingw = "master:2a3ae35de9c846354a07ac1a2db51382cd290c02" Initialising tasks: 100% |###############################################################################################################################################################| Time: 0:00:02 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Tasks Summary: Attempted 1973 tasks of which 10 didn't need to be rerun and all succeeded. I did a clean build, wiping sstate & tmp. Is this build ran on regular base on AB? Please keep the tarball for a while, it may come in handy. I will try to run the build in a debian container next week. (In reply to comment #3) > I did a clean build, wiping sstate & tmp. > Is this build ran on regular base on AB? It is now, yes. It's part of the nightly-qa-extras which is triggered every time a "nightly" build is run. > Please keep the tarball for a while, it may come in handy. Will do. > I will try to run the build in a debian container next week. Interesting, I wonder if it's specific to debian-testing. It appears the question has been answered. I ran the build many times but I cannot reproduce the problem. I don't want to close the bug as WORKSFORME, but I don't think the bug warrants medium+ importance. (I assume here the bug was not observed in AB again) BTW, the attached log file is "run.do_compile" instead of the more useful "log.do_compile". But I guess the gist of compile log is in this bug report. Cannot reproduce, tried numerous times, so closing as WORKSFORME We can re-open if we run into this again. |