Bug 7544

Summary: [Build Appliance] Hob exception when build an image
Product: [Build System, Metadata & Runtime] Runtime Reporter: Yi Zhao <yi.zhao>
Component: build-applianceAssignee: Cristian Iorga <cristian.iorga>
Status: RESOLVED WORKSFORME QA Contact: Yi Zhao <yi.zhao>
Severity: normal    
Priority: Undecided CC: alexandru.c.georgescu, ke.zou, yi.zhao, zhangle.yang
Version: 1.8   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
hob error none

Description Yi Zhao 2015-03-31 08:57:58 UTC 
Created attachment 2461 [details]
hob error

Image location: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.8_M4.rc1/build-appliance/

Git rev: master/8b3d3e7c957ad06c390886487f69aeb8e145da6a

Host: Ubuntu 12.04 x86-64
VMware Player 7.0.0 build-2305329

Sometimes I got a hob exception when build an image. Please see the attached pic. This issue can not reproduced every time.
Comment 1 Cristian Iorga 2015-03-31 09:40:59 UTC 
More context is needed. What is needed is a more precise context in which the bug is happening. For example, when that exception is thrown, is the current bitbake task always do_rm_work_all on core-image-minimal recipe?
Given also the fact that the issue is not 100% reproducible, is not easy to get a grip of the issue at hand and also find the root cause.
Please add the necessary info.
Also, when that exception is thrown, please extract the system log (dmesg) and add it here.
Comment 2 Yi Zhao 2015-04-02 06:58:56 UTC 
(In reply to comment #1)
> More context is needed. What is needed is a more precise context in which
> the bug is happening. For example, when that exception is thrown, is the
> current bitbake task always do_rm_work_all on core-image-minimal recipe?
> Given also the fact that the issue is not 100% reproducible, is not easy to
> get a grip of the issue at hand and also find the root cause.
> Please add the necessary info.
> Also, when that exception is thrown, please extract the system log (dmesg)
> and add it here.

I tried several times, but can not reproduced it again. I will keep one eye on this in the next testing.
Comment 3 Cristian Iorga 2015-04-02 14:54:20 UTC 
Please re-open if it's reproducible again.