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

[Xen-devel] [xen-unstable test] 24728: trouble: broken/fail/pass

flight 24728 xen-unstable real [real]

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-freebsd10-amd64  3 host-install(3)      broken REGR. vs. 24723

Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-xl-sedf      3 host-install(3)         broken REGR. vs. 24723
 test-amd64-i386-qemuu-rhel6hvm-amd  3 host-install(3)        broken like 24723
 test-amd64-i386-xl-qemuu-win7-amd64  7 windows-install         fail like 24719

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-armhf-armhf-xl           9 guest-start                  fail   never pass
 test-amd64-i386-xend-winxpsp3 16 leak-check/check             fail  never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop             fail never pass
 test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop              fail never pass
 test-amd64-amd64-xl-win7-amd64 13 guest-stop                   fail never pass
 test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop               fail never pass
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop         fail never pass
 test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check        fail never pass
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 13 guest-stop         fail never pass
 test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop               fail never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop               fail never pass
 test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop             fail never pass
 test-amd64-amd64-xl-winxpsp3 13 guest-stop                   fail   never pass
 test-amd64-i386-xl-win7-amd64 13 guest-stop                   fail  never pass

version targeted for testing:
 xen                  ff1745d5882b7356ea423709919e46e55c31b615
baseline version:
 xen                  04d31ea1b1caeac7f77b5d18910761abd540545f

People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Anthony PERARD <anthony.perard@xxxxxxxxxx>
  Ian Campbell <Ian.Campbell@xxxxxxxxxx>
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Julien Grall <julien.grall@xxxxxxxxxx>
  Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  Olaf Hering <olaf@xxxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>

 build-amd64-xend                                             pass    
 build-i386-xend                                              pass    
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl                                          pass    
 test-armhf-armhf-xl                                          fail    
 test-amd64-i386-xl                                           pass    
 test-amd64-i386-rhel6hvm-amd                                 pass    
 test-amd64-i386-qemut-rhel6hvm-amd                           pass    
 test-amd64-i386-qemuu-rhel6hvm-amd                           broken  
 test-amd64-i386-freebsd10-amd64                              broken  
 test-amd64-amd64-xl-qemut-win7-amd64                         fail    
 test-amd64-i386-xl-qemut-win7-amd64                          fail    
 test-amd64-amd64-xl-qemuu-win7-amd64                         fail    
 test-amd64-i386-xl-qemuu-win7-amd64                          fail    
 test-amd64-amd64-xl-win7-amd64                               fail    
 test-amd64-i386-xl-win7-amd64                                fail    
 test-amd64-i386-xl-credit2                                   pass    
 test-amd64-i386-freebsd10-i386                               pass    
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-i386-rhel6hvm-intel                               pass    
 test-amd64-i386-qemut-rhel6hvm-intel                         pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-i386-xl-multivcpu                                 pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-amd64-amd64-xl-sedf-pin                                 pass    
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           pass    
 test-amd64-amd64-xl-sedf                                     broken  
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     fail    
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     fail    
 test-amd64-i386-xl-winxpsp3-vcpus1                           fail    
 test-amd64-i386-xend-qemut-winxpsp3                          fail    
 test-amd64-amd64-xl-qemut-winxpsp3                           fail    
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail    
 test-amd64-i386-xend-winxpsp3                                fail    
 test-amd64-amd64-xl-winxpsp3                                 fail    

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 ff1745d5882b7356ea423709919e46e55c31b615
Author: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date:   Thu Jan 16 15:27:59 2014 +0000

    tools: libxl: do not set the PoD target on ARM
    ARM does not implemented PoD and so returns ENOSYS from 
    The correct solution here would be to check for ENOSYS in libxl, 
    xc_domain_set_pod_target suffers from the same broken error reporting as the
    rest of libxc and throws away the errno.
    So for now conditionally define xc_domain_set_pod_target to return success
    (which is what PoD does if nothing needs doing). xc_domain_get_pod_target 
    errno==-1 and returns -1, which matches the broken error reporting of the
    existing function. It appears to have no in tree callers in any case.
    The conditional should be removed once libxc has been fixed.
    This makes ballooning (xl mem-set) work for ARM domains.
    Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    Acked-by: Julien Grall <julien.grall@xxxxxxxxxx>
    Cc: george.dunlap@xxxxxxxxxx

commit 5224a733d3bd4d0db3548712047506c50487085e
Author: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date:   Fri Jan 24 14:23:07 2014 +0000

    xen: arm: correct use of find_next_bit
    find_next_bit takes a "const unsigned long *" but forcing a cast of an
    "uint32_t *" throws away the alignment constraints and ends up causing an
    alignment fault on arm64 if the input happened to be 4 but not 8 byte 
    Instead of casting use a temporary variable of the right type.
    I've had a look around for similar constructs and the only thing I found was
    maintenance_interrupt which cases a uint64_t down to an unsigned long, which
    although perhaps not best advised is safe I think.
    This was observed with the AArch64 Linaro toolchain 2013.12 but I think that
    is just coincidental due to subtle changes to the stack layout etc.
    Reported-by: Fu Wei <fu.wei@xxxxxxxxxx>
    Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Acked-by: Julien Grall <julien.grall@xxxxxxxxxx>

commit ea527eda9e1f7a8dcd4cf799c01c4b11468e952f
Author: Julien Grall <julien.grall@xxxxxxxxxx>
Date:   Fri Jan 31 22:22:45 2014 +0000

    xen/arm: Directly return NULL if Xen fails to allocate domain struct
    The current implementation of alloc_domain_struct, dereference the newly
    allocated pointer even if the allocation has failed.
    Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

commit 46b5f0fd1fe7a49fb993fbad8a1fa232e2253afc
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Mon Jan 27 17:53:38 2014 +0000

    libxc: fix claim mode when creating HVM guest
    The original code is wrong because:
    * claim mode wants to know the total number of pages needed while
      original code provides the additional number of pages needed.
    * if pod is enabled memory will already be allocated by the time we try
      to claim memory.
    So the fix would be:
    * move claim mode before actual memory allocation.
    * pass the right number of pages to hypervisor.
    The "right number of pages" should be number of pages of target memory
    minus VGA_HOLE_SIZE, regardless of whether PoD is enabled.
    This fixes bug #32.
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
    Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
    Cc: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit 3f4218742f5efc7c89fc1c61af546942f9d2dbb8
Author: Olaf Hering <olaf@xxxxxxxxx>
Date:   Tue Jan 28 19:12:16 2014 +0100

    xl: update check-xl-disk-parse to handle backend_domname
    Signed-off-by: Olaf Hering <olaf@xxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

commit 834eec157a20746135054d519b8e4ccd3f6a8088
Author: Anthony PERARD <anthony.perard@xxxxxxxxxx>
Date:   Tue Jan 28 16:03:03 2014 +0000

    doc: Better documentation about the usbdevice=['host:bus.addr'] format
    Signed-off-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    [ ijc -- minor wording tweak ]

commit c2ba706c44813342269eb5cb2288552dc5f2a9a7
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Mon Jan 27 16:25:24 2014 +0000

    tools/libxc: goto correct label on error paths
    Both of these "goto finish;" statements are actually errors, and need to 
    out;" instead, which will correctly destroy the domain and return an error,
    rather than trying to finish the migration (and in at least one scenario,
    return success).
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
    CC: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    CC: George Dunlap <george.dunlap@xxxxxxxxxxxxx>

commit af172d655c3900822d1f710ac13ee38ee9d482d2
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Feb 4 09:22:12 2014 +0100

    x86/domctl: don't ignore errors from vmce_restore_vcpu()
    What started out as a simple cleanup patch (eliminating the redundant
    check of domctl->cmd before setting "copyback", which as a result
    turned the "ext_vcpucontext_out" label useless) revealed a bug in the
    handling of XEN_DOMCTL_set_ext_vcpucontext.
    Fix this, retaining the cleanup, and at once dropping a stale comment
    and an accompanying formatting issue.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
(qemu changes not included)

Xen-devel mailing list



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