WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [xen-unstable test] 6413: regressions - FAIL
From: xen.org <ian.jackson@xxxxxxxxxxxxx>
Date: Mon, 14 Mar 2011 01:59:27 +0000
Cc: ian.jackson@xxxxxxxxxxxxx
Delivery-date: Sun, 13 Mar 2011 19:00:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
flight 6413 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/6413/

Regressions :-(

Tests which did not succeed and are blocking:
 test-amd64-amd64-pair         8 xen-boot/dst_host          fail REGR. vs. 6396
 test-amd64-amd64-pair         7 xen-boot/src_host          fail REGR. vs. 6396
 test-amd64-amd64-xl-win       5 xen-boot                   fail REGR. vs. 6396
 test-amd64-i386-rhel6hvm-intel  5 xen-boot                 fail REGR. vs. 6396
 test-amd64-i386-win-vcpus1    5 xen-boot                   fail REGR. vs. 6396
 test-amd64-xcpkern-i386-pair  8 xen-boot/dst_host          fail REGR. vs. 6396
 test-amd64-xcpkern-i386-pair  7 xen-boot/src_host          fail REGR. vs. 6396
 test-amd64-xcpkern-i386-pv    5 xen-boot                   fail REGR. vs. 6396
 test-amd64-xcpkern-i386-rhel6hvm-intel  5 xen-boot         fail REGR. vs. 6396
 test-amd64-xcpkern-i386-xl    5 xen-boot                   fail REGR. vs. 6396
 test-i386-i386-pv             5 xen-boot                   fail REGR. vs. 6396
 test-i386-i386-xl-win         5 xen-boot                   fail REGR. vs. 6396
 test-i386-xcpkern-i386-xl     5 xen-boot                   fail REGR. vs. 6396

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-i386-rhel6hvm-amd  8 guest-saverestore            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-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-xcpkern-i386-win   16 leak-check/check             fail   never pass

version targeted for testing:
 xen                  84bacd800bf8
baseline version:
 xen                  a8fee4ad3ad0

------------------------------------------------------------
People who touched revisions under test:
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxxxx>
  Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
  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                                   fail     
 test-i386-xcpkern-i386-xl                                    fail     
 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                                        fail     
 test-amd64-i386-pair                                         pass     
 test-i386-i386-pair                                          pass     
 test-amd64-xcpkern-i386-pair                                 fail     
 test-i386-xcpkern-i386-pair                                  pass     
 test-amd64-amd64-pv                                          pass     
 test-amd64-i386-pv                                           pass     
 test-i386-i386-pv                                            fail     
 test-amd64-xcpkern-i386-pv                                   fail     
 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:   23033:84bacd800bf8
tag:         tip
user:        Jan Beulich <jbeulich@xxxxxxxxxx>
date:        Sat Mar 12 13:20:51 2011 +0000
    
    x86/HPET: adjust types
    
    'unsigned int' is better suited as an array index on x86-64.
    
    'u32' produces better code than 'unsigned long' on x86-64, so use the
    former for storing 32-bit values read from the hardware.
    
    this_cpu() uses an implicit smp_processor_id(), and hence using
    per_cpu() when the result of smp_processor_id() is already available
    is more efficient.
    
    Fold one case of cpu_isset()+cpu_clear() into cpu_test_and_clear().
    
    Drop the unused return value of evt_do_broadcast().
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    Acked-by: Wei Gang <gang.wei@xxxxxxxxx>
    
    
changeset:   23032:ac572e1df261
user:        Jan Beulich <jbeulich@xxxxxxxxxx>
date:        Sat Mar 12 13:20:11 2011 +0000
    
    x86/HPET: use dynamic allocation for hpet_events[]
    
    Typically there are far less than 32 counters available, and hence
    there's no use in wasting the memory on (almost) every system.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    Acked-by: Wei Gang <gang.wei@xxxxxxxxx>
    
    
changeset:   23031:5263151fba9b
user:        Jan Beulich <jbeulich@xxxxxxxxxx>
date:        Sat Mar 12 13:19:34 2011 +0000
    
    x86/HPET: cleanup
    
    - separate init and resume code paths (so that the [larger] init parts
      can go init .init.* sections)
    - drop the separate legacy_hpet_event object, as we can easily re-use
      the first slot of hpet_events[] for that purpose (the whole array is
      otherwise unused when the legacy code is being used)
    - use section placement attributes where reasonable
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    Acked-by: Wei Gang <gang.wei@xxxxxxxxx>
    
    
changeset:   23030:87aa1277eae0
user:        Jan Beulich <jbeulich@xxxxxxxxxx>
date:        Sat Mar 12 13:19:02 2011 +0000
    
    x86/HPET: fix initialization order
    
    At least the legacy path can enter its interrupt handler callout while
    initialization is still in progress - that handler checks whether
    ->event_handler is non-NULL, and hence all other initialization must
    happen before setting this field.
    
    Do the same to the MSI initialization just in case (and to keep the
    code in sync).
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    
    
changeset:   23029:a8fee4ad3ad0
user:        Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
date:        Fri Mar 11 18:22:23 2011 +0000
    
    libxl: do not try to use blktap with qdisk
    
    libxl_device_disk_add tries to use blktap when available even for qdisk
    devices, this patch fixes it.
    
    Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    
    
(qemu changes not included)

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