[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [qemu-upstream-4.2-testing test] 17115: regressions - trouble: broken/fail/pass

I think this is because the qemu tag has not been changed.


--On 7 March 2013 05:10:48 +0000 "xen.org" <ian.jackson@xxxxxxxxxxxxx> wrote:

flight 17115 qemu-upstream-4.2-testing real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-i386-i386-xl-qemuu-winxpsp3 7 windows-install fail in 17084 REGR. vs. 

Tests which are failing intermittently (not blocking):
 test-i386-i386-xl-qemuu-winxpsp3  3 host-install(3)       broken pass in 17084

Tests which did not succeed, but are not blocking:
 build-armhf                   4 xen-build                    fail   never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop             fail never pass
 test-amd64-amd64-xl-qemuu-win 13 guest-stop                   fail  never pass
 test-amd64-i386-qemuu-win-vcpus1 16 leak-check/check           fail never pass
 test-amd64-i386-qemuu-win    16 leak-check/check             fail   never pass
 test-i386-i386-qemuu-win     16 leak-check/check             fail   never pass
 test-amd64-i386-xl-qemuu-win-vcpus1 13 guest-stop              fail never pass
 test-amd64-i386-xend-qemuu-winxpsp3 16 leak-check/check        fail never pass
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 13 guest-stop         fail never pass
 test-i386-i386-xl-qemuu-win  12 guest-localmigrate/x10       fail   never pass
 test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop               fail never pass
 test-amd64-amd64-qemuu-win   16 leak-check/check             fail   never pass
 test-amd64-i386-xl-qemuu-win7-amd64 13 guest-stop              fail never pass

version targeted for testing:
 qemuu                eccc68722696864fc4823f048c7be58d11281b97
baseline version:
 qemuu                70454385eeee6f0b3f7a9eddca9f7340b5060824

People who touched revisions under test:
  Alex Bligh <alex@xxxxxxxxxxx>
  Anthony PERARD <anthony.perard@xxxxxxxxxx>
  Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>

 build-amd64                                                  pass
 build-armhf                                                  fail
 build-i386                                                   pass
 build-amd64-oldkern                                          pass
 build-i386-oldkern                                           pass
 build-amd64-pvops                                            pass
 build-i386-pvops                                             pass
 test-amd64-i386-qemuu-rhel6hvm-amd                           pass
 test-amd64-amd64-xl-qemuu-win7-amd64                         fail
 test-amd64-i386-xl-qemuu-win7-amd64                          fail
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass
 test-amd64-i386-qemuu-win-vcpus1                             fail
 test-amd64-i386-xl-qemuu-win-vcpus1                          fail
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     fail
 test-amd64-amd64-qemuu-win                                   fail
 test-amd64-i386-qemuu-win                                    fail
 test-i386-i386-qemuu-win                                     fail
 test-amd64-amd64-xl-qemuu-win                                fail
 test-i386-i386-xl-qemuu-win                                  fail
 test-amd64-i386-xend-qemuu-winxpsp3                          fail
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail
 test-i386-i386-xl-qemuu-winxpsp3                             broken

sg-report-flight on woking.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images

Logs, config files, etc. are available at

Test harness code can be found at

Not pushing.

commit eccc68722696864fc4823f048c7be58d11281b97
Author: Anthony PERARD <anthony.perard@xxxxxxxxxx>
Date:   Thu Feb 21 12:16:42 2013 +0000

    xen: Set the vram dirty when an error occurs.

    If the call to xc_hvm_track_dirty_vram() fails, then we set dirtybit on all 
    video ram. This case happens during migration.

    Backport of 8aba7dc02d5660df7e7d8651304b3079908358be

    This backport is less clean that it might be because there is no
    memory_region_set_dirty that copes with more than one page in 4.2,
    and the case where the call to xc_hvm_track_dirty_vram is
    successful also needs to ensure xen_modified_memory is
    called (which would on unstable have been done within

    Signed-off-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
    Acked-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
    Signed-off-by: Alex Bligh <alex@xxxxxxxxxxx>

Xen-devel mailing list

Alex Bligh

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.