Bug 3797

Summary: [Autobuilder] qemuimage-testlib causes build failure
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Bogdan Marinescu <bogdan.a.marinescu>
Component: configurationAssignee: Darren Hart <dvhart>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Low CC: sgw
Version: unspecified   
Target Milestone: 1.4   
Hardware: Other   
OS: x86   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Bogdan Marinescu 2013-01-25 09:43:41 UTC 
| spawn ssh -o UserKnownHostsFile=/tmp/tmp.crqbDVmX7Y root@192.168.7.2 /sbin/poweroff
| The authenticity of host '192.168.7.2 (192.168.7.2)' can't be established.
| RSA key fingerprint is e7:a1:db:b3:b3:f8:ba:cc:21:8c:0b:1f:71:ec:6d:b8.
| Are you sure you want to continue connecting (yes/no)? yes
| Warning: Permanently added '192.168.7.2' (RSA) to the list of known hosts.
| root@192.168.7.2's password:
| 	Test_Info: Shutdown Test FAIL
| UID        PID  PPID  C STIME TTY          TIME CMD
| 1006     17163 17155  0 23:07 pts/0    00:00:00 bash -c OE_TMPDIR=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/scripts/runqemu /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/deploy/images/bzImage-qemux86.bin /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/work/qemux86-poky-linux/core-image-sato/1.0-r0/qemuimagetest/tmp/core-image-sato-qemux86-test.ext3 && /bin/sleep 60
| UID        PID  PPID  C STIME TTY          TIME CMD
| 1006     17165 17163  0 23:07 pts/0    00:00:00 /bin/bash /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/scripts/runqemu /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/deploy/images/bzImage-qemux86.bin /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/work/qemux86-poky-linux/core-image-sato/1.0-r0/qemuimagetest/tmp/core-image-sato-qemux86-test.ext3
| UID        PID  PPID  C STIME TTY          TIME CMD
| 1006     17216 17165 23 23:07 pts/0    00:02:22 /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/deploy/images/bzImage-qemux86.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -hda /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/work/qemux86-poky-linux/core-image-sato/1.0-r0/qemuimagetest/tmp/core-image-sato-qemux86-test.ext3 -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot -m 128 --append vga=0 root=/dev/hda rw mem=128M ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1
| UID        PID  PPID  C STIME TTY          TIME CMD
| /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/scripts/qemuimage-testlib: line 257: kill: (17165) - No such process
| /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/scripts/qemuimage-testlib: line 262: kill: (17155) - No such process
| NOTE: 	Test Result for qemux86 core-image-sato
| NOTE: 	Testcase       PASS           FAIL           NORESULT
| NOTE: 	SSH            1              0              0
| NOTE: 	SCP            1              0              0
| NOTE: 	dmesg          1              0              0
| NOTE: 	smart_help     1              0              0
| NOTE: 	smart_query    1              0              0
| NOTE: 	rpm_query      1              0              0
| NOTE: 	connman        1              0              0
| NOTE: 	shutdown       0              1              0
| DEBUG: Python function do_qemuimagetest_standalone finished
| ERROR: Function failed: Some testcases fail, pls. check test result and test log!!!
NOTE: recipe core-image-sato-1.0-r0: task do_qemuimagetest_standalone: Failed

More information : http://autobuilder.yoctoproject.org:8010/builders/nightly-x86/builds/886/steps/shell_39/logs/stdio
Comment 1 Saul Wold 2013-01-25 19:19:24 UTC 
This is a transient timeout on the sanity tests, it happens on the shutdown, when the halt hangs or exits abnormally.
Comment 2 Richard Purdie 2013-02-07 00:25:16 UTC 
This looks like its the issue Darren was investigating. Darren, I'm assuming this can be marked as a dup of another bug?
Comment 3 Darren Hart 2013-02-09 00:03:30 UTC 
This has the same report pattern as Bug 3806:

| NOTE: 	shutdown       0              1              0

And seems likely to be a duplicate. Marking as such.

*** This bug has been marked as a duplicate of bug 3806 ***