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

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



flight 10511 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/10511/

Regressions :-(

Tests which did not succeed and are blocking:
 test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail in 10504 REGR. vs. 
10491

Tests which are failing intermittently (not blocking):
 test-amd64-amd64-xl-sedf     13 guest-localmigrate.2        fail pass in 10504
 test-i386-i386-win            7 windows-install             fail pass in 10504
 test-amd64-i386-win           7 windows-install    fail in 10504 pass in 10511
 test-amd64-amd64-xl-winxpsp3  7 windows-install    fail in 10504 pass in 10511

Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-amd64-i386-rhel6hvm-intel  9 guest-start.2                fail never pass
 test-amd64-i386-rhel6hvm-amd  9 guest-start.2                fail   never pass
 test-amd64-i386-xl-win7-amd64 13 guest-stop                   fail  never pass
 test-amd64-i386-win-vcpus1   16 leak-check/check             fail   never pass
 test-amd64-i386-win          16 leak-check/check             fail   never pass
 test-amd64-amd64-xl-win      13 guest-stop                   fail   never pass
 test-amd64-i386-xl-win-vcpus1 13 guest-stop                   fail  never pass
 test-i386-i386-xl-win        13 guest-stop                   fail   never pass
 test-amd64-amd64-xl-winxpsp3 13 guest-stop                   fail   never pass
 test-i386-i386-xl-winxpsp3   13 guest-stop                   fail   never pass
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 test-amd64-amd64-xl-win7-amd64 13 guest-stop                   fail never pass
 test-amd64-i386-xend-winxpsp3 16 leak-check/check             fail  never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop               fail never pass
 test-i386-i386-win           16 leak-check/check      fail in 10504 never pass

version targeted for testing:
 xen                  01c8b27e3d7d
baseline version:
 xen                  03138a08366b

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Christoph Egger <Christoph.Egger@xxxxxxx>
  Ian Campbell <ian.campbell@xxxxxxxxxx>
  Ian Jackson <ian.jackson.citrix.com>
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Keir Fraser <keir@xxxxxxx>
  Liu, Jinsong <jinsong.liu@xxxxxxxxx>
------------------------------------------------------------

jobs:
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl                                          pass    
 test-amd64-i386-xl                                           pass    
 test-i386-i386-xl                                            pass    
 test-amd64-i386-rhel6hvm-amd                                 fail    
 test-amd64-amd64-xl-win7-amd64                               fail    
 test-amd64-i386-xl-win7-amd64                                fail    
 test-amd64-i386-xl-credit2                                   pass    
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-i386-rhel6hvm-intel                               fail    
 test-amd64-i386-xl-multivcpu                                 pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-i386-i386-pair                                          pass    
 test-amd64-amd64-xl-sedf-pin                                 pass    
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           pass    
 test-i386-i386-pv                                            pass    
 test-amd64-amd64-xl-sedf                                     fail    
 test-amd64-i386-win-vcpus1                                   fail    
 test-amd64-i386-xl-win-vcpus1                                fail    
 test-amd64-i386-xl-winxpsp3-vcpus1                           fail    
 test-amd64-amd64-win                                         fail    
 test-amd64-i386-win                                          fail    
 test-i386-i386-win                                           fail    
 test-amd64-amd64-xl-win                                      fail    
 test-i386-i386-xl-win                                        fail    
 test-amd64-i386-xend-winxpsp3                                fail    
 test-amd64-amd64-xl-winxpsp3                                 fail    
 test-i386-i386-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
    http://www.chiark.greenend.org.uk/~xensrcts/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
changeset:   24416:01c8b27e3d7d
tag:         tip
user:        Ian Campbell <ian.campbell@xxxxxxxxxx>
date:        Thu Dec 15 16:56:21 2011 +0000
    
    libxl: remove stubdom device model save file when destroying stubdom
    
    /var/lib/xen/qemu-save.<domid> is created when the stub domain is started
    (connected to a stubdom console) and is used to save the device model state 
on
    suspend/migrate but never cleaned up.
    
    Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    
    
changeset:   24415:27736c7944b9
user:        Ian Campbell <ian.campbell@xxxxxxxxxx>
date:        Thu Dec 15 16:53:52 2011 +0000
    
    oxenstored: Always log something at start of day (if logging enabled at all)
    
    Otherwise at the default level we rarely log anything at all.
    
    A completely empty log file is a good sign, but only if you know you are
    looking in the right place...
    
    Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    
    
changeset:   24414:de4034343b3a
user:        Ian Campbell <ian.campbell@xxxxxxxxxx>
date:        Thu Dec 15 16:52:22 2011 +0000
    
    oxenstored: install configuration file
    
    First though:
      - Move it to /etc/xen/oxenstored.conf.
      - Use /var/run/xenstored.pid as default pid file
      - Disable test-eagain "Randomly failed a transaction with EAGAIN. Used for
        testing Xs user". Doesn't sound fun by default...
    
    Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    
    
changeset:   24413:a9d61ea9973a
user:        Ian Campbell <ian.campbell@xxxxxxxxxx>
date:        Thu Dec 15 16:50:36 2011 +0000
    
    oxenstored: handle unknown operations by returning an error to the client
    
    Previous an unknown operation would be decoded as a Not_found exception 
which
    would bubble all the way up to the try ... with surrounding the call to
    main_loop where it would be logged and ignored.
    
    This would leave the guest hanging waiting for a response to the invalid
    request.
    
    Instead introduce a specific "Invalid" operation. Higher level 
functionality,
    such as Process.process_packet, already handles operations which are not
    understood with an error reply due to the final wildcard entry in
    Process.function_of_type but explicitly handle Invalid this way to make it
    clear what is going on.
    
    Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    
    
changeset:   24412:99caac2e35df
user:        Jan Beulich <jbeulich@xxxxxxxx>
date:        Thu Dec 15 14:28:45 2011 +0100
    
    x86/AMD: use correct shift count when merging model and stepping
    
    ... for legacy errata matching.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    
    
changeset:   24411:ca5f588bd203
user:        Christoph Egger <Christoph.Egger@xxxxxxx>
date:        Thu Dec 15 11:00:09 2011 +0100
    
    x86/ucode: fix for AMD Fam15 CPUs
    
    Remove hardcoded maximum size a microcode patch can have. This is
    dynamic now.
    
    The microcode patch for family15h can be larger than 2048 bytes and
    gets silently truncated.
    
    Signed-off-by: Christoph Egger <Christoph.Egger@xxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24410:25f8952313ae
user:        Liu, Jinsong <jinsong.liu@xxxxxxxxx>
date:        Thu Dec 15 10:58:53 2011 +0100
    
    x86/MCE: add more strict sanity check of one SRAR case
    
    When RIPV = EIPV = 0, it's a little bit tricky. It may be an asynchronic 
error, currently we have no way to precisely locate whether the error occur at 
guest or hypervisor.
    To avoid handling error in wrong way, we treat it as unrecovered.
    
    Signed-off-by: Liu, Jinsong <jinsong.liu@xxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24409:0cd9f3e5f3e0
user:        Liu, Jinsong <jinsong.liu@xxxxxxxxx>
date:        Thu Dec 15 10:54:51 2011 +0100
    
    x86/MCE: add SRAR handler
    
    Currently Intel SDM add 2 kinds of MCE SRAR errors:
    1). Data Load error, error code = 0x134
    2). Instruction Fetch error, error code = 0x150
    This patch add handler to these new SRAR errors.
    It based on existed mce infrastructure, add code to handle SRAR specific 
error.
    
    Signed-off-by: Liu, Jinsong <jinsong.liu@xxxxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24408:5d2dd48bce21
user:        Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
date:        Wed Dec 14 17:53:54 2011 +0100
    
    XLAT.lst whitespace fix.
    
    Replace spaces with tabs to be in line with file format.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24407:03138a08366b
user:        Ian Campbell <ian.campbell@xxxxxxxxxx>
date:        Fri Dec 09 16:19:36 2011 +0000
    
    oxenstored: log Errors and Warnings by default.
    
    Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson.citrix.com>
    Committed-by: Ian Jackson <ian.jackson.citrix.com>
    
    
========================================
commit 54e24021005458ad0a361c1d83011b751726a94b
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Thu Dec 8 16:38:06 2011 +0000

    qemu_get_timer: Provide a comment about the behaviour on ts==NULL
    
    Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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