<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>4191</bug_id>
          
          <creation_ts>2013-04-04 09:02:06 +0000</creation_ts>
          <short_desc>[Autobuilder] Random Sanity Failures</short_desc>
          <delta_ts>2013-04-08 15:22:30 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>5</classification_id>
          <classification>Infrastructure</classification>
          <product>AutoBuilder</product>
          <component>autobuilder</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.4 M6</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Bogdan Marinescu">bogdan.a.marinescu</reporter>
          <assigned_to name="Richard Purdie">richard.purdie</assigned_to>
          <cc>infras.ab.watcher</cc>
    
    <cc>Infras.watcher</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>31498</commentid>
    <comment_count>0</comment_count>
    <who name="Bogdan Marinescu">bogdan.a.marinescu</who>
    <bug_when>2013-04-04 09:02:06 +0000</bug_when>
    <thetext>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 &apos;1&apos;
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&apos;t find a better category.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>31643</commentid>
    <comment_count>1</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2013-04-06 22:38:13 +0000</bug_when>
    <thetext>http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=6d4d42d63db4c3fcffd831ce359599f3ee1d710e is the best guess fix for this at this point.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>31702</commentid>
    <comment_count>2</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2013-04-08 15:22:30 +0000</bug_when>
    <thetext>We&apos;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.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>