| Summary: | Yocto 2.1M3 rc1 Build Appliance: bitbake core-image-minimal with command-line failed | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Runtime | Reporter: | Ke Zou <ke.zou> |
| Component: | build-appliance | Assignee: | Juro Bystricky <juro.bystricky> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | alexandru.c.georgescu, yi.zhao, zhangle.yang |
| Version: | 2.1 | ||
| Target Milestone: | 2.1 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ke Zou
2016-03-21 09:12:59 UTC
I downloaded the Build Appliance from http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M3.rc1/build-appliance/ Uncompressed and ran using VMplayer/Ubuntu (had to configure the network first). Then, in Terminal <2> I ran $ bitbake core-image-minimal I did get an error: Unable to create '/home/builder/poky/bitbake/lib/bb/pysh/pyshtables.py' [Errno 22] invalid mode ('w') or filename '/home/builder/poky/bitbake/lib/bb/pysh/pyshtables.py' I also got a two warnings, but those are expected: 1. Host distribution not validated 2. Build host not configured to process I/O statistics So it would indicate some permissions/ownership is not set correctly. I will look into that. However, the build continued (still building, takes hours to finish it). I believe the above error was there even with previous (HOB) BA version, just not directly visible. In any case, I could not reproduce the originally reported bug. Can you please provide more details? (exact steps to reproduce, screenshots etc.) I could not reproduce the bug, although there were some permissions related errors. The FS seems to be corrupted, for example I cannot create a directory in /home/builder/poky: # cd /home/builder/poky # mkdir aaa mkdir: cannot create directory 'aaa': Invalid argument (just in poky, I can create directories anywhere else though) So I think the image on the web is somehow corrupted and hence the problems (Yocto_Build_Appliance-20160314012314.zip). Correction. The image is not corrupted, it is a permission error. Same error(s) were observed when the image was rebuilt locally. Merged: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=7d251f75ebfb6d61c8576a1d7b371f1a0b82f75e Tested the patch by building core-image-minimal in Build Appliance (using VMplayer) and then booting the resulting image in qemu (outside BA). verified with YOCTO build 2.1M3 rc2 |