Hi Joshua, I noticed for 2.5 M1 rc3, nightly-x86 failed during testimage (Sanity Test), due to runqemu error. Is this expected? Shall QA move on to initialize the QA for this rc3?
Thank you very much for your attention and help! Thanks, Yeoh Ee Peng https://autobuilder.yocto.io/builders/nightly-x86/builds/703 ERROR: core-image-sato-sdk-1.0-r0 do_testimage: Qemu pid didn't appear in 120 seconds (01/04/18 17:54:45) ERROR: core-image-sato-1.0-r0 do_testimage: Qemu pid didn't appear in 120 seconds (01/04/18 17:54:45) WARNING: core-image-sato-sdk-1.0-r0 do_testimage: Qemu ended unexpectedly, dump data from host is in /tmp/oe-saved-tests/201801041754_qemu WARNING: core-image-sato-1.0-r0 do_testimage: Qemu ended unexpectedly, dump data from host is in /tmp/oe-saved-tests/201801041754_qemu ERROR: core-image-sato-sdk-1.0-r0 do_testimage: Output from runqemu: runqemu - INFO - Continuing with the following parameters: runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap1.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Using preconfigured tap device tap2 runqemu - INFO - If this is not intended, touch /tmp/qemu-tap-locks/tap2.skip to make runqemu skip tap2. runqemu - INFO - Network configuration: 192.168.7.6::192.168.7.5:255.255.255.0 runqemu - INFO - Running /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86/build/build/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/qemu-system-i386 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:06 -netdev tap,id=net0,ifname=tap2,script=no,downscript=no -drive file=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86/build/build/tmp/deploy/images/qemux86/core-image-sato-sdk-qemux86.ext4,if=virtio,format=raw -vga vmware -show-cursor -usb -device usb-tablet -device virtio-rng-pci -serial tcp:127.0.0.1:57033 -pidfile pidfile_32833 -cpu pentium2 -enable-kvm -m 256 -serial tcp:127.0.0.1:33999 -snapshot -kernel /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86/build/build/tmp/deploy/images/qemux86/bzImage--4.12.18+git0+b66a4f9730_558fe84d69-r0.2-qemux86-20180102174658.bin -append 'root=/dev/vda rw highres=off clocksource=kvm-clock hpet=disable noapic nolapic mem=256M ip=192.168.7.6::192.168.7.5:255.255.255.0 vga=0 uvesafb.mode_option=640x480-32 oprofile.timer=1 uvesafb.task_timeout=-1 console=tty1 console=ttyS0,115200n8 printk.time=1' runqemu - ERROR - Failed to run qemu: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory qemu-system-i386: failed to initialize KVM: Cannot allocate memory -----Original Message----- From: Lock, Joshua G Sent: Thursday, January 4, 2018 11:42 PM To: pokybu...@debian8.yocto.io; yocto@yoctoproject.org Cc: pi...@toganlabs.com; Perez Carranza, Jose <jose.perez.carra...@intel.com>; Cruz, Libertad <libertad.c...@intel.com>; ota...@ossystems.com.br; Zhao, Yi (Wind River) <yi.z...@windriver.com>; Graydon, Tracy <tracy.gray...@intel.com>; Sangal, Apoorv <apoorv.san...@intel.com>; Yeoh, Ee Peng <ee.peng.y...@intel.com>; Chan, Aaron Chun Yew <aaron.chun.yew.c...@intel.com>; Chang, Rebecca Swee Fun <rebecca.swee.fun.ch...@intel.com>; Ang, Chin Huat <chin.huat....@intel.com> Subject: Re: Release Candidate Build for yocto-2.5_M1.rc2 now available. This build had a couple of failures, I'm going to spin another rc. QA: please don't take any action with this build. Joshua On 04/01/18 15:35, pokybu...@debian8.yocto.io wrote: > > A release candidate build for yocto-2.5_M1.rc2 is now available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-2.5_M1.rc2 > > > Please begin QA on this build as soon as possible. > > > Build hash information: > meta-intel : 1580913674bc84c8e6c10cf855dbf38d2ee8f3d2 > meta-qt4 : f313dbee2ac3d5fcc9801407947d3cb6cfb90b5d > meta-mingw : a2c5fb82e5595d5bb56b579b7c93147c4fb065a5 > meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f > meta-gplv2 : a0f8716d07324e945f0462b82f9309fa0934af17 > poky : 8f436af94648c8c14244b71183e7da5f6cd09813 > > > This is an automated message from > The Yocto Project Autobuilder > Git: git://git.yoctoproject.org/yocto-autobuilder > Email: joshua.g.l...@intel.com > -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
