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

[xen.org <ian.jackson@xxxxxxxxxxxxx>]

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

Regressions :-(

Tests which did not succeed and are blocking:
 test-amd64-i386-rhel6hvm-amd  7 redhat-install             fail REGR. vs. 6310
 test-amd64-xcpkern-i386-xl-credit2  8 debian-fixup         fail REGR. vs. 6310

Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 test-amd64-amd64-xl-win      13 guest-stop                   fail   never pass
 test-amd64-i386-rhel6hvm-intel  8 guest-saverestore            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-i386-xl-win-vcpus1 13 guest-stop                   fail  never pass
 test-amd64-xcpkern-i386-rhel6hvm-amd  8 guest-saverestore      fail never pass
 test-amd64-xcpkern-i386-rhel6hvm-intel  8 guest-saverestore    fail never pass
 test-amd64-xcpkern-i386-win  16 leak-check/check             fail   never pass
 test-amd64-xcpkern-i386-xl-win 13 guest-stop                   fail never pass
 test-i386-i386-win           16 leak-check/check             fail   never pass
 test-i386-i386-xl-win        13 guest-stop                   fail   never pass
 test-i386-xcpkern-i386-win   16 leak-check/check             fail   never pass

version targeted for testing:
 xen                  a1108fe57086
baseline version:
 xen                  0662bff7dabb

------------------------------------------------------------
People who touched revisions under test:
  Keir Fraser <keir@xxxxxxx>
  Wei Gang <gang.wei@xxxxxxxxx>
------------------------------------------------------------

jobs:
 build-i386-xcpkern                                           pass     
 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-xcpkern-i386-xl                                   pass     
 test-i386-xcpkern-i386-xl                                    pass     
 test-amd64-i386-rhel6hvm-amd                                 fail     
 test-amd64-xcpkern-i386-rhel6hvm-amd                         fail     
 test-amd64-i386-xl-credit2                                   pass     
 test-amd64-xcpkern-i386-xl-credit2                           fail     
 test-amd64-i386-rhel6hvm-intel                               fail     
 test-amd64-xcpkern-i386-rhel6hvm-intel                       fail     
 test-amd64-i386-xl-multivcpu                                 pass     
 test-amd64-xcpkern-i386-xl-multivcpu                         pass     
 test-amd64-amd64-pair                                        pass     
 test-amd64-i386-pair                                         pass     
 test-i386-i386-pair                                          pass     
 test-amd64-xcpkern-i386-pair                                 pass     
 test-i386-xcpkern-i386-pair                                  pass     
 test-amd64-amd64-pv                                          pass     
 test-amd64-i386-pv                                           pass     
 test-i386-i386-pv                                            pass     
 test-amd64-xcpkern-i386-pv                                   pass     
 test-i386-xcpkern-i386-pv                                    pass     
 test-amd64-i386-win-vcpus1                                   fail     
 test-amd64-i386-xl-win-vcpus1                                fail     
 test-amd64-amd64-win                                         fail     
 test-amd64-i386-win                                          fail     
 test-i386-i386-win                                           fail     
 test-amd64-xcpkern-i386-win                                  fail     
 test-i386-xcpkern-i386-win                                   fail     
 test-amd64-amd64-xl-win                                      fail     
 test-i386-i386-xl-win                                        fail     
 test-amd64-xcpkern-i386-xl-win                               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:   22976:a1108fe57086
tag:         tip
user:        Keir Fraser <keir@xxxxxxx>
date:        Sat Mar 05 11:36:21 2011 +0000
    
    sched_credit: Hold lock while dump scheduler info
    
    Dump runq with debug key 'r' may cause dead loop like below:
    
    (XEN) active vcpus:
    (XEN)     1: [1.0] pri=0 flags=0 cpu=0 credit=263 [w=256]
    (XEN)     2: [0.2] pri=0 flags=0 cpu=5 credit=284 [w=256]
    (XEN)     3: [0.2] pri=0 flags=0 cpu=5 credit=282 [w=256]
    ...
    (XEN)  xxxxx: [0.2] pri=0 flags=0 cpu=2 credit=54 [w=256]
    ...
    (XEN)  xxxxx: [0.2] pri=0 flags=0 cpu=3 credit=-48 [w=256]
    ...
    
    This means the active vcpu 0.2 became non-active with the active list
    element empty just after it was accessed in the loop '2:'.
    
    We should always hold a lock before access scheduler related list,
    even in the debug purpose dump code.
    
    Signed-off-by: Wei Gang <gang.wei@xxxxxxxxx>
    
    
changeset:   22975:d3d29df8f082
user:        Keir Fraser <keir@xxxxxxx>
date:        Sat Mar 05 11:34:41 2011 +0000
    
    x86: On CPU offline, fix master waiting for slave to be fully dead.
    
    On two back-to-back CPU offline operations, on second offline the
    cpu_state var will be CPU_STATE_DEAD from the first offline. Hence
    __cpu_die() will incorrectly not wait for the second slave to fully
    die and set cpu_state itself.
    
    The fix is to set cpu_state to a new value, CPU_STATE_DYING, earlier
    during CPU offline, before __cpu_die() starts to execute.
    
    Original diagnosis and patch by Liu, Jinsong <jinsong.liu@xxxxxxxxx>
    
    Signed-off-by: Keir Fraser <keir@xxxxxxx>
    
    
changeset:   22974:0662bff7dabb
user:        Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
date:        Fri Mar 04 17:33:32 2011 +0000
    
    Added signature for changeset 6241fa0ad1a9
    
    
(qemu changes not included)

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