| Test_Info: IP 192.168.7.4 is not up | Test_Info: Wait for Qemu Network up | PING 192.168.7.4 (192.168.7.4) 56(84) bytes of data. | From 192.168.7.3 icmp_seq=1 Destination Host Unreachable | | --- 192.168.7.4 ping statistics --- | 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms | | 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 Build Configuration: BB_VERSION = "1.16.0" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "qemuarm" DISTRO = "poky" DISTRO_VERSION = "1.3+snapshot-20121024" TUNE_FEATURES = "armv5 dsp thumb arm926ejs" TARGET_FPU = "soft" meta meta-yocto = "master:33440ee70623394d06a4b214c2be10788cba6d08" meta-qt3 = "master:ccfc85ed3b6c3880a6142adf53fa63856bc6d7d7" meta-yocto-bsp = "master:33440ee70623394d06a4b214c2be10788cba6d08" Autobuilder link: http://autobuilder.yoctoproject.org:8010/builders/nightly-arm/builds/708/steps/shell_39
This is a transient failure, we need to determine how the test if failing. As in are we really not shutting down, is the connection to the VM stil there, what's happening behind the scenes.
I think Yi can help with this.
Not reproducible and logs are no longer available.