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

[Xen-devel] [xen-unstable test] 32503: regressions - FAIL

flight 32503 xen-unstable real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-pair   18 guest-migrate/dst_host/src_host fail REGR. vs. 32392

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-xl          10 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt      9 guest-start                  fail   never pass
 test-amd64-i386-libvirt       9 guest-start                  fail   never pass
 test-armhf-armhf-libvirt      9 guest-start                  fail   never pass
 test-amd64-amd64-xl-pvh-amd   9 guest-start                  fail   never pass
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-amd64-amd64-xl-pvh-intel  9 guest-start                  fail  never pass
 test-amd64-i386-xl-qemut-winxpsp3 14 guest-stop                fail never pass
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-stop         fail never pass
 test-amd64-i386-xl-qemuu-winxpsp3 14 guest-stop                fail never pass
 test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop             fail never pass
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop         fail never pass
 test-amd64-i386-xl-qemuu-win7-amd64 14 guest-stop              fail never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-stop             fail never pass
 test-amd64-i386-xl-qemut-win7-amd64 14 guest-stop              fail never pass
 test-amd64-i386-xl-win7-amd64 14 guest-stop                   fail  never pass
 test-amd64-amd64-xl-win7-amd64 14 guest-stop                   fail never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 14 guest-stop               fail never pass
 test-amd64-amd64-xl-winxpsp3 14 guest-stop                   fail   never pass
 test-amd64-amd64-xl-qemut-winxpsp3 14 guest-stop               fail never pass
 test-amd64-i386-xl-winxpsp3  14 guest-stop                   fail   never pass
 test-amd64-amd64-xl-qemuu-winxpsp3 14 guest-stop               fail never pass

version targeted for testing:
 xen                  36174af3fbeb1b662c0eadbfa193e77f68cc955b
baseline version:
 xen                  2676bc915157ab474ee478d929b0928cf696b385

People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  George Dunlap <george.dunlap@xxxxxxxxxxxxx>
  Ian Campbell <ian.campbell@xxxxxxxxxx>
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
  Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  M A Young <m.a.young@xxxxxxxxxxxx>
  Michael Young <m.a.young@xxxxxxxxxxxx>
  Oleksandr Dmytryshyn <oleksandr.dmytryshyn@xxxxxxxxxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>

 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-armhf-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 build-amd64-rumpuserxen                                      pass    
 build-i386-rumpuserxen                                       pass    
 test-amd64-amd64-xl                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-amd64-i386-xl                                           pass    
 test-amd64-amd64-xl-pvh-amd                                  fail    
 test-amd64-i386-rhel6hvm-amd                                 pass    
 test-amd64-i386-qemut-rhel6hvm-amd                           pass    
 test-amd64-i386-qemuu-rhel6hvm-amd                           pass    
 test-amd64-amd64-xl-qemut-debianhvm-amd64                    pass    
 test-amd64-i386-xl-qemut-debianhvm-amd64                     pass    
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    pass    
 test-amd64-i386-xl-qemuu-debianhvm-amd64                     pass    
 test-amd64-i386-freebsd10-amd64                              pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    
 test-amd64-amd64-rumpuserxen-amd64                           pass    
 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-i386-rumpuserxen-i386                             pass    
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-amd64-xl-pvh-intel                                fail    
 test-amd64-i386-rhel6hvm-intel                               pass    
 test-amd64-i386-qemut-rhel6hvm-intel                         pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-amd64-libvirt                                     fail    
 test-armhf-armhf-libvirt                                     fail    
 test-amd64-i386-libvirt                                      fail    
 test-amd64-i386-xl-multivcpu                                 pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         fail    
 test-amd64-amd64-xl-sedf-pin                                 pass    
 test-amd64-amd64-xl-sedf                                     pass    
 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-amd64-xl-qemut-winxpsp3                           fail    
 test-amd64-i386-xl-qemut-winxpsp3                            fail    
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail    
 test-amd64-i386-xl-qemuu-winxpsp3                            fail    
 test-amd64-amd64-xl-winxpsp3                                 fail    
 test-amd64-i386-xl-winxpsp3                                  fail    

sg-report-flight on osstest.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 36174af3fbeb1b662c0eadbfa193e77f68cc955b
Author: M A Young <m.a.young@xxxxxxxxxxxx>
Date:   Thu Dec 18 10:02:16 2014 +0000

    tools/xl: fix segfault in xl migrate --debug
    If differences are found during the verification phase of xl migrate
    --debug then it is likely to crash with a segfault because the bogus
    pagebuf->pfn_types[pfn] is used in a print statement instead of
    pfn_type[pfn] .
    Signed-off-by: Michael Young <m.a.young@xxxxxxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

commit 7e88c23239591e2638bcc944151a660fcd53495b
Author: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
Date:   Tue Dec 9 14:04:19 2014 +0000

    libxl: Tell qemu to use raw format when using a tapdisk
    At the moment libxl unconditinally passes the underlying file format
    to qemu in the device string.  However, when tapdisk is in use,
    tapdisk handles the underlying format and presents qemu with
    effectively a raw disk.  When qemu looks at the tapdisk block device
    and doesn't find the image format it was looking for, it will fail.
    This effectively means that tapdisk cannot be used with HVM domains at
    the moment except for raw files.
    Instead, if we're using a tapdisk backend, tell qemu to use a raw file
    Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    [ ijc -- nuked extra blank line ]

commit 09b7ff1a118f5e920ef12f5592f3ce991218962a
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Mon Dec 15 10:56:24 2014 +0000

    xl: print message to stdout when (!debug && dryrun)
    In commit d36a3734a ("xl: fix migration failure with xl migrate
    --debug"), message is printed to stderr for both debug mode
    and dryrun mode. That caused rdname() in xendomains fails to parse
    domain name since it's expecting input from xl's stdout.
    So this patch separates those two cases. If xl is running in debug mode,
    then message is printed to stderr; if xl is running in dryrun mode and
    debug is not enabled, message is printed to stdout. This will fix
    xendomains and other scripts that use "xl create --dryrun", as well as
    not re-introducing the old bug fixed in d36a3734a.
    Reported-by: Mark Pryor <tlviewer@xxxxxxxxx>
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Cc: M A Young <m.a.young@xxxxxxxxxxxx>
    Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Release-Acked-by: Konrad Wilk <konrad.wilk@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

commit afa3fd8753c944f37c1cd182d5ad7c436c7614da
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Fri Dec 12 18:26:02 2014 +0000

    docs/commandline: Minor formatting fixes and clarifications
    `font` had a trailing single quote which was out of place.
    `gnttab_max_frames` was missing escapes for the underscores which caused the
    underscores to take their markdown meaning, causing 'max' in the middle to 
    italicised.  Escape the underscores, and make all command line parameters
    bold, to be consistent with the existing style.
    Clarify how the default for `nmi` changes between debug and non debug builds
    of Xen.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    CC: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
    CC: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    CC: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

commit 3f727fb1a7d5f3be2513ab2e692b067075325fb3
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Tue Dec 9 16:43:22 2014 +0000

    python/xc: Fix multiple issues in pyflask_context_to_sid()
    The error handling from a failed memory allocation should return
    PyErr_SetFromErrno(xc_error_obj); rather than simply calling it and 
    to the memcpy() below, with the dest pointer being NULL.
    Coverity also complains about passing a non-NUL terminated string to
    xc_flask_context_to_sid().  xc_flask_context_to_sid() doesn't actually take 
    NUL terminated string, but it does take a char* which, in context, used to 
    a string, which is why Coverity complains.
    One solution would be to use strdup(ctx) which is simpler than a
    strlen()/malloc()/memcpy() combo, which would result in a NUL-terminated
    string being used with xc_flask_context_to_sid().
    However, ctx is strictly an input to the hypercall and is not mutated along
    the way.  Both these issues can be fixed, and the error logic simplified, by
    not duplicating ctx in the first place.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Coverity-IDs: 1055305 1055721
    Acked-by: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
    CC: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    CC: Wei Liu <wei.liu2@xxxxxxxxxx>
    CC: Xen Coverity Team <coverity@xxxxxxx>

commit dcd84861b0b01b8895716d4c803c9d24c31c8cab
Author: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@xxxxxxxxxxxxxxx>
Date:   Mon Dec 8 15:51:47 2014 +0200

    xen/serial: setup UART idle mode for OMAP
    The UART is not able to receive bytes when idle mode is not configured
    properly, therefore setup the UART with autoidle and wakeup enabled.
    Older Linux kernels (for example 3.8) configure hwmods for all devices
    even if the device tree nodes for those devices is absent in device
    tree, thus UART idle mode is configured too.  With such kernels we can
    workaround the issue by adding a fake node in the UART containing this
    MMIO range, which is therefore mapped by Xen to dom0, which
    reconfigures the UART, causing things to work normally.
    Newer Linux Kernels (3.12 and beyond) do not configure idle mode for
    UART and so this hack no longer works.
    Signed-off-by: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@xxxxxxxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    [ ijc -- updated commit message as discussed ]

commit 6c9b27d3f363889718e7e046511383927f257095
Merge: 2676bc9 05fecc3
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Mon Dec 15 17:40:12 2014 +0000

    Merge tag '4.5.0-rc4' into staging
    Xen 4.5.0 RC4

commit 05fecc382e129731c6595268a377f4bff879f694
Author: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date:   Mon Dec 15 11:35:59 2014 -0500

    Xen-4.5.0-rc4: Update tag for qemu-xen.
    QEMU-traditional has nothing new, so stay at rc1 there.
    Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@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®.