Bug 4191

Summary:	[Autobuilder] Random Sanity Failures
Product:	[Infrastructure] AutoBuilder	Reporter:	Bogdan Marinescu <bogdan.a.marinescu>
Component:	autobuilder	Assignee:	Richard Purdie <richard.purdie>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	infras.ab.watcher, Infras.watcher, sgw
Version:	unspecified
Target Milestone:	1.4 M6
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Bogdan Marinescu 2013-04-04 09:02:06 UTC

http://autobuilder.yoctoproject.org:8011/builders/nightly-arm/builds/84/steps/Running%20Sanity%20Tests/logs/stdio

| Test_Info: IP 192.168.7.2 is not up
| Test_Info: Wait for Qemu Network up
| Test_Info: IP 192.168.7.2 is not up
| Test_Info: Wait for Qemu Network up
| Test_Info: IP 192.168.7.2 is not up
| Test_Info: Wait for Qemu Network up
| Test_Info: IP 192.168.7.2 is not up
| Test_Info: Wait for Qemu Network up
| Test_Info: Qemu or its network is not up in 120 seconds
| Saving 11931 192.168.7.2 to /srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-arm/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0-r0/qemuimagetest/tmp/target_ip
| Test_Info: Boot Test FAIL
| killing 4796
| killing 11931
| 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-new/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.

Not sure this is actually related to the autobuilder, but I couldn't find a better category.

Comment 1 Richard Purdie 2013-04-06 22:38:13 UTC

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=6d4d42d63db4c3fcffd831ce359599f3ee1d710e is the best guess fix for this at this point.

Comment 2 Richard Purdie 2013-04-08 15:22:30 UTC

We've not seen this particular problem since this fix went in so we can assume it was a timeout related problem and is now resolved.