[Yocto-builds] buildbot failure in Yocto on nightly-arm

Saul Wold sgw at linux.intel.com
Tue Oct 2 18:00:27 PDT 2012


On 10/02/2012 04:48 PM, yocto-builds at yoctoproject.org wrote:
>
>         Build status: FAILURE
>
> Buildslave for this Build: *ab05*
> Complete logs for all build steps:
> http://autobuilder.yoctoproject.org:8010/builders/nightly-arm/builds/675
> Build Reason: Triggerable(nightly-arm)
> Build Source Stamp: *[branch master]
> 8609051d8d4f9fa565eb48418a87fa0048613374*
> /Detailed log of last build step:/
> http://autobuilder.yoctoproject.org:8010/builders/nightly-arm/builds/675/steps/shell_39/logs/stdio
>
>
>
>         Last 20 lines of "shell_39.stdio" Error log:
>

I ran a standalone sanity test of qemuarm core-image-minimal just now on 
ab05, which is where this failed.  I looked at the logs to see the 
difference and one thing I noted was that there was already a qemu 
running, possibly for another builder

Are we having somekind of resource starvation if we have 2 qemu 
processes running at the same time?

in 
build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_qemuimagetest_standalone.12180

The Test_info shows:

	Test_Info: There is at least one Qemu process running
	Test_Info: Begin to check if qemu network is up

Michael, can you check into this somehow?  I was able to log in as 
pokybuild on ab05 and run 2 sanitytests and was able to get it to fail.

I went into each build dir and ran:


~/yocto-autobuilder/yocto-slave/nightly-ppc/build
. oe-core-init-env
export DISPLAY=localhost:1
  MACHINE=qemuppc bitbake core-image-sato -c qemuimagetest_standalone

- Let that start for a minute and confirm qemu is running

~/yocto-autobuilder/yocto-slave/nightly-arm/build
. oe-core-init-env
export DISPLAY=localhost:1
  MACHINE=qemuarm bitbake core-image-minimal -c qemuimagetest_standalone

this will then fail pinging the newly created machine, not sure if there 
is a tap/tun issue?

Beth, question about yocto-autobuilder-sanitytest script, why does it 
remove the auto.conf, instead of preserving/restoring it?  I found if I 
wanted to run it multiple times I needed to set the MACHINE somehow 
since it kept removing the auto.conf file.


Thanks
	Sau!
> |
> | Test_Info: IP 192.168.7.4 is not up
> | Test_Info: Wait for Qemu Network up
> | Test_Info: Qemu or its network is not up in 120 seconds
> | Test_Info: Boot Test FAIL
> | UID PID PPID C STIME TTY TIME CMD
> | 1006 12203 12196 0 21:07 pts/2 00:00:00 bash -c
> OE_TMPDIR=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/scripts/runqemu
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/deploy/images/zImage-qemuarm.bin
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal-1.0-r0/qemuimagetest/tmp/core-image-minimal-qemuarm-test.ext3
> && /bin/sleep 60
> | UID PID PPID C STIME TTY TIME CMD
> | 1006 12204 12203 0 21:07 pts/2 00:00:00 /bin/bash
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/scripts/runqemu
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/deploy/images/zImage-qemuarm.bin
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal-1.0-r0/qemuimagetest/tmp/core-image-minimal-qemuarm-test.ext3
> | UID PID PPID C STIME TTY TIME CMD
> | 1006 12260 12204 1 21:07 pts/2 00:00:02
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-arm
> -kernel
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/deploy/images/zImage-qemuarm.bin
> -net nic,vlan=0 -net tap,vlan=0,ifname=tap1,script=no,downscript=no -M
> versatilepb -hda
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal-1.0-r0/qemuimagetest/tmp/core-image-minimal-qemuarm-test.ext3
> -no-reboot -show-cursor -usb -usbdevice wacom-tablet -no-reboot -m 128
> --append root=/dev/sda rw console=ttyAMA0,115200 console=tty
> ip=192.168.7.4::192.168.7.3:255.255.255.0 mem=128M highres=off
> | UID PID PPID C STIME TTY TIME CMD
> |
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/scripts/qemuimage-testlib:
> line 262: kill: (12196) - No such process
> | NOTE: Test Result for qemuarm core-image-minimal
> | NOTE: Testcase PASS FAIL NORESULT
> | NOTE: Boot 0 1 0
> | DEBUG: Python function do_qemuimagetest_standalone finished
> | ERROR: Function failed: Some testcases fail, pls. check test result
> and test log!!!
> ERROR: Task 0
> (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/meta/recipes-core/images/core-image-minimal.bb,
> do_qemuimagetest_standalone) failed with exit code '1'
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
>
>
> *-The Yocto BuildBot*
>
>
> _______________________________________________
> Yocto-builds mailing list
> Yocto-builds at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-builds
>



More information about the Yocto-builds mailing list