Bug 2249 - [Hob2] Image is not created when doing a rebuild
Summary: [Hob2] Image is not created when doing a rebuild
Status: RESOLVED FIXED
Alias: None
Product: Hob
Classification: Build System, Metadata & Runtime
Component: hob (show other bugs)
Version: 1.2
Hardware: x86 Multiple
: Medium major
Target Milestone: 1.2 M4
Assignee: Dongxiao Xu
QA Contact:
URL:
Whiteboard: Patch submitted
Depends on:
Blocks:
 
Reported: 2012-04-05 17:48 UTC by Saul Wold
Modified: 2012-04-16 00:09 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
The template to reproduce. (8.92 KB, application/octet-stream)
2012-04-13 09:59 UTC, Shane Wang 		no flags Details
The first error if Hob enables "No provider" (76.66 KB, image/png)
2012-04-13 10:00 UTC, Shane Wang 		no flags Details
The second error if Hob enables "No provider" (85.84 KB, image/png)
2012-04-13 10:01 UTC, Shane Wang 		no flags Details
The third error if Hob enables "No provider" (81.78 KB, image/png)
2012-04-13 10:01 UTC, Shane Wang 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Saul Wold 2012-04-05 17:48:56 UTC 
There have been a couple of occasions when I have attempted to build an image and it completes, but there is no image available and no errors reported.  I start hob in an existing build area and select the machine and core-image-sato (I have previously built other images in this builddir, but manually).  

I watch the Log, it seems to be re-building base-files and then completes without actually building the image.  But it goes to the Image details screen as if it completed successfully with no images listed.

I tried with both a template that I saved and with a fresh core-image-sato image, both failed to actually build the image
Comment 1 Jiajun Xu 2012-04-10 15:24:44 UTC 
In my testing against commit 190f6d791d51aaa4cfb9f1cf932bc205ff674fb5, there is no such issue met.
Comment 2 Shane Wang 2012-04-13 09:58:08 UTC 
Saul gave a template to reproduce. I can reproduce. That is because "No provider" problem. In Hob, we disabled the error to pop up and we should disable. Otherwise, for instance, we even can't build qemu-arm. Hopefully the bitbake side can fix the "No provider" issue so we can enable it in the end.
Comment 3 Shane Wang 2012-04-13 09:59:53 UTC 
Created attachment 466 [details]
The template to reproduce.
Comment 4 Shane Wang 2012-04-13 10:00:32 UTC 
Created attachment 467 [details]
The first error if Hob enables "No provider"
Comment 5 Shane Wang 2012-04-13 10:01:00 UTC 
Created attachment 468 [details]
The second error if Hob enables "No provider"
Comment 6 Shane Wang 2012-04-13 10:01:33 UTC 
Created attachment 469 [details]
The third error if Hob enables "No provider"
Comment 7 Shane Wang 2012-04-15 00:49:31 UTC 
When I use bitbake command to build sato on qemuppc, it reports:

yocto-build5@yocto-build5:/distro/testing$ bitbake core-image-sato
Parsing recipes: 100% |#########################################| Time: 00:00:10
Parsing of 829 .bb files complete (0 cached, 829 parsed). 1105 targets, 35 skipped, 0 masked, 0 errors.

OE Build Configuration:
BB_VERSION        = "1.15.1"
TARGET_ARCH       = "powerpc"
TARGET_OS         = "linux"
MACHINE           = "qemuppc"
DISTRO            = "poky"
DISTRO_VERSION    = "1.1+snapshot-20120415"
TUNE_FEATURES     = "m32 fpu-hard ppc603e"
TARGET_FPU        = ""
meta
meta-yocto        = "hob_0415:008c0b573f59eb39fd545222bd0ff32442b34301"

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'syslinux'
ERROR: syslinux was skipped: incompatible with host powerpc-poky-linux (not in COMPATIBLE_HOST)
ERROR: Required build target 'core-image-sato' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-sato', 'syslinux']

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
Comment 8 Shane Wang 2012-04-15 00:51:17 UTC 
But we think in that case we shouldn't get users to build success page. Will fix that.