Created attachment 4388 [details] wrong log file Steps to Reproduce : 1. Get build applaince image from following link https://autobuilder.yocto.io/pub/releases/yocto-2.6.rc1/build-appliance/Yocto_Build_Appliance.zip 2. boot the build appliance image in vmware. 3. Set MACHINE to qemux86 and add the following line to conf/local.conf : SRCREV_pn-build-appliance-image = "$ {AUTOREV} " 4. Run "bitbake build-appliance-image" Logs are attached for reference : Source/WebCore/CMakeFiles/WebCore.dir/_/_/DerivedSources/WebCore/unified-sources/UnifiedSource22.cpp.o -c DerivedSources/WebCore/unified-sources/UnifiedSource22.cpp ninja: build stopped: subcommand failed. WARNING: /home/builder/poky/build/tmp/work/i586-poky-linux/webkitgtk/2.20.5-r0/temp/run.do_compile.65203:1 exit 1 from 'eval ${DESTDIR:+DESTDIR=$ {DESTDIR} }VERBOSE=1 cmake --build '/home/builder/poky/build/tmp/work/i586-poky-linux/webkitgtk/2.20.5-r0/build' "$@" – -j 2' ERROR: Function failed: do_compile (log file is located at /home/builder/poky/build/tmp/work/i586-poky-linux/webkitgtk/2.20.5-r0/temp/log.do_compile.65203) Result with 2.6M3RC1 : Build-Appliance was blocked in previous release.
new log file attached.
Created attachment 4389 [details] do_compile_logs new log file attached.
Some questions: How much memory did this VM have? The key error is "i586-poky-linux-g++: fatal error: Killed signal terminated program cc1plus" which sounds like it could be the OOM killer. Was there a report in dmesg? Does this issue reproduce the same way each time? Can the build continue if you rerun the bitbake command?
In vm have 4gb memory. cc1plus issue is reported in dmesg log also issue is produced each time. build cannot continue.
I think we need to test two things: Does this issue go away if the VM memory is increased, e.g. 8GB? Does this issue occur with a qemux86-64 build appliance? or building for qemux86-64?
We tried with VM memory with 8GB, after compiling 80% VM Ware application is crashed. We are building qemux86.
This bug is present in Yocto 2.4.4.rc1. logs are attached.
Created attachment 4395 [details] yocto_2.4.1
(In reply to comment #5) > I think we need to test two things: > > Does this issue go away if the VM memory is increased, e.g. 8GB? > > Does this issue occur with a qemux86-64 build appliance? or building for > qemux86-64? We are building qemux86 this issue is occur in qemux86. Can I try for qemux86-64..?
Richard, Has you question been answered? Do you have more questions?
This bug is still coming in Yocto 2.5.2.rc1.
Created attachment 4408 [details] do_compile_logs_2.5.2 yocto 2.5.2 : webkitgtk do_compile logs are attached.
This bug is still coming in Yocto 2.7 M
Created attachment 4415 [details] do_compile_logs do_compile log file attached.
This bug still present is yocto-2.6.1.rc1. do_compile log file is attached.
Created attachment 4422 [details] do_compile_logs webkitgtk do_compile log file is attached
This bug is repeated in yocto-2.7_M2.rc1 webkitgtk do_compile failed with exit code 1
This bug is repeated in 2.7 M3.rc1
Minimum/Safe required RAM is 8G for webkit, now with qemux86, do we have PAE enabled kernel where it can use >4G for RAM ?
(In reply to comment #19) > Minimum/Safe required RAM is 8G for webkit, now with qemux86, do we have PAE > enabled kernel where it can use >4G for RAM ? vm have 4gb memory. We tried with VM memory with 8GB, after compiling 80% VM Ware application is crashed.
This bug is still repeated in 2.6.2.rc3
This bug is coming in 2.5.3.rc3 build failed to compile webkitgtk package
This issue is observed in current release 2.7.rc2
I think that we should change the test so that we bitbake a smaller image inside the VM: maybe core-image-base. Enough to exercise the build but *not webkit*.
We dropped epiphany from the build-appliance image which means it won't build webkitgtk and hence we won't see this resource issue: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=c7770d5c1c9e4e0c30b89cf72f3dc6596a719910