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

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

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

Regressions :-(

Tests which did not succeed and are blocking:
 test-i386-i386-xl            18 leak-check/check           fail REGR. vs. 4586
 test-i386-xcpkern-i386-pair   7 xen-boot/src_host          fail REGR. vs. 4586

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          18 leak-check/check             fail    like 4586
 test-amd64-i386-rhel6hvm-amd  8 guest-saverestore            fail   never pass
 test-amd64-i386-rhel6hvm-intel  8 guest-saverestore            fail never pass
 test-amd64-i386-win          16 leak-check/check             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-i386-i386-win           16 leak-check/check             fail   never pass
 test-i386-xcpkern-i386-win   16 leak-check/check             fail   never pass

version targeted for testing:
 xen                  63fd6f886f49
baseline version:
 xen                  7b4c82f07281

------------------------------------------------------------
People who touched revisions under test:
  Christoph Egger <Christoph.Egger@xxxxxxx>
  Chun Yan Liu <cyliu@xxxxxxxxxx>
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
------------------------------------------------------------

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                                          fail     
 test-amd64-i386-xl                                           pass     
 test-i386-i386-xl                                            fail     
 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                           pass     
 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                                  fail     
 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-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     


------------------------------------------------------------
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:   22654:63fd6f886f49
tag:         tip
user:        Christoph Egger <Christoph.Egger@xxxxxxx>
date:        Thu Jan 06 14:25:10 2011 +0000
    
    libxl: Implement libxl_basename()
    
    This patch implements libxl_basename() as a portable replacement
    for GNU vs. POSIX basename.
    
    Signed-off-by: Christoph Egger <Christoph.Egger@xxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    
    
changeset:   22653:7b4c82f07281
user:        Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
date:        Wed Jan 05 23:54:15 2011 +0000
    
    QEMU_TAG update
    
    
========================================
commit 99d53fbb69d3e03be61ae10506a304a3d08d792f
Author: Chun Yan Liu <cyliu@xxxxxxxxxx>
Date:   Wed Jan 5 23:48:36 2011 +0000

    fix '|' key display problem in en-us with altgr processing
    
    Commit f95d202ed644 handles altgr-insert problem.  Unfortunately, with
    that patch, there is a problem in En-us keyboard: '|' (bar) cannot be
    displayed. After checking keymap files, we found there are two
    definitions to "bar" in en-us: bar 0x56 altgr (in "common") bar 0x2b
    shift (in "en-us") First line is actually invalid in en-us
    lanuage. The 2nd definition will cover the 1st one.
    
    The previous change in didn't consider multi-definition case. It scans
    keymap files, if keysym needs altgr, it will records that, after that,
    if keysym is pressed but altgr not pressed, it will add an altgr press
    opeartion. It is correct if all keysyms are unique and valid. But in
    the above multi-definition case, there is problem: when reading bar
    0x56 altgr (in "common") it will record altgr needed, but in fact,
    that definition won't be used, it always use the 2nd definition and
    won't need altgr. Then if the keysym is pressed, the code will still
    add an altgr press operation, that will cause problem.
    
    So, if we cannot avoid multi-definition in keymap files, the altgr
    flag (whether altgr needed or not) should also be refreshed according
    to the 2nd defintion. In the above case, when reading the 1st line, it
    records altgr needed; then reading 2nd line, 2nd definition will cover
    the 1st, meanwhile the altgr flag should be reset (the 2nd definition
    doesn't need altgr, so altgr flag should be removed.)
    
    Following patch supplements f95d202ed644, and solve the
    problem.
    
    Signed-off-by: Chun Yan Liu <cyliu@xxxxxxxxxx>
    Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

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