Bug 4825 - [Autobuilder][multilib] Qemu or its network is not up in 50 seconds
Summary: [Autobuilder][multilib] Qemu or its network is not up in 50 seconds
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.5
Assignee: Stefan Stanacar
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-07-08 13:50 UTC by Ioana Grigoropol
Modified: 2013-08-08 12:55 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
log multilib (188.23 KB, application/octet-stream)
2013-07-08 13:50 UTC, Ioana Grigoropol 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ioana Grigoropol 2013-07-08 13:50:45 UTC 
Created attachment 1315 [details]
log multilib

Running qemu-system-x86_64...
| /srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-multilib/build/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-x86_64 -kernel /srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-multilib/build/build/tmp/deploy/images/bzImage-qemux86-64.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap1,script=no,downscript=no -hda /srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-multilib/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/qemuimagetest/tmp/core-image-sato-qemux86-64-test.ext3 -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot -m 128 --append "vga=0 uvesafb.mode_option=640x480-32 root=/dev/hda rw mem=128M ip=192.168.7.4::192.168.7.3:255.255.255.0 oprofile.timer=1 "
| 	Test_Info: Qemu or its network is not up in 50 seconds
| Saving 16662 192.168.7.4 to /srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-multilib/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/qemuimagetest/tmp/target_ip
| 	Test_Info: Dmesg Test FAIL, Pls. check above error log
| 	Test_Info: Do not kill the qemu process and use it for later testing (step 3 of 4)
| Saving 16662 192.168.7.4 to /srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-multilib/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/qemuimagetest/tmp/target_ip
| NOTE: Run shutdown test in scenario sanity
| 	Test_Info: rootfs image extension selected: ext3
| 	Test_Info: Begin to check if qemu network is up
| QEMUPID is 16776
| Target IP is 192.168.7.4
| 	Test_Info: IP 192.168.7.4 is not up
| 	Test_Info: Wait for Qemu Network up
| 	Test_Info: IP 192.168.7.4 is not up
Comment 1 Saul Wold 2013-07-16 17:11:28 UTC 
This is QA Test related
Comment 2 Stefan Stanacar 2013-07-17 11:53:48 UTC 
Just a note: this is the old qemuimagetest implementation, so given that nothing changed there recently I don't think it was a test fail, and indeed the image failed to boot on the AB.

However, I've built a multilib ipk image (the nightly-multilib target has multiple builds, without the CreateAutoConf log I don't know which one was, I asssumed the ipk one) on the commit found in the log (eaa5df34af42b6a37f6506847d0f3ef6ba0d298a) and I couldn't reproduce this locally.
Comment 3 Stefan Stanacar 2013-08-08 12:55:54 UTC 
I wasn't able to reproduce this at the time and I haven't seen it in recent multilib builds.