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-4.0-testing test] 8662: regressions - trouble: blocked/

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [xen-4.0-testing test] 8662: regressions - trouble: blocked/broken/fail/pass
From: xen.org <ian.jackson@xxxxxxxxxxxxx>
Date: Wed, 17 Aug 2011 02:28:02 +0100
Cc: ian.jackson@xxxxxxxxxxxxx
Delivery-date: Tue, 16 Aug 2011 18:29:16 -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 8662 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/8662/

Regressions :-(

Tests which did not succeed and are blocking:
 build-i386-pvops              2 host-install(2)              broken
 test-amd64-amd64-xl           9 guest-start                fail REGR. vs. 8293

Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
 test-i386-i386-win            1 xen-build-check(1)           blocked  n/a
 test-i386-i386-xl-win         1 xen-build-check(1)           blocked  n/a
 test-i386-i386-xl             1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-win-vcpus1    1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl-credit2    1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl            1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl-multivcpu  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-win           1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-rhel6hvm-intel  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl-win-vcpus1  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-rhel6hvm-amd  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-pv            1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-pair          1 xen-build-check(1)           blocked  n/a
 test-amd64-amd64-xl-win       7 windows-install              fail   never pass
 test-amd64-amd64-xl-pcipt-intel  8 debian-fixup                fail never pass
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 test-i386-i386-pv             1 xen-build-check(1)           blocked  n/a
 test-i386-i386-pair           1 xen-build-check(1)           blocked  n/a

version targeted for testing:
 xen                  cb453558fd2b
baseline version:
 xen                  f09ab04f614e

------------------------------------------------------------
People who touched revisions under test:
  Keir Fraser <keir@xxxxxxx>
  Tim Deegan <Tim.Deegan@xxxxxxxxxx>
------------------------------------------------------------

jobs:
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             broken  
 test-amd64-amd64-xl                                          fail    
 test-amd64-i386-xl                                           blocked 
 test-i386-i386-xl                                            blocked 
 test-amd64-i386-rhel6hvm-amd                                 blocked 
 test-amd64-i386-xl-credit2                                   blocked 
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-i386-rhel6hvm-intel                               blocked 
 test-amd64-i386-xl-multivcpu                                 blocked 
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         blocked 
 test-i386-i386-pair                                          blocked 
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           blocked 
 test-i386-i386-pv                                            blocked 
 test-amd64-i386-win-vcpus1                                   blocked 
 test-amd64-i386-xl-win-vcpus1                                blocked 
 test-amd64-amd64-win                                         fail    
 test-amd64-i386-win                                          blocked 
 test-i386-i386-win                                           blocked 
 test-amd64-amd64-xl-win                                      fail    
 test-i386-i386-xl-win                                        blocked 


------------------------------------------------------------
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:   21525:cb453558fd2b
tag:         tip
user:        Tim Deegan <Tim.Deegan@xxxxxxxxxx>
date:        Tue Aug 16 15:27:06 2011 +0100
    
    VT-d: always clean up dpci timers.
    
    If a VM has all its PCI devices deassigned, need_iommu(d) becomes
    false but it might still have DPCI EOI timers that were init_timer()d
    but not yet kill_timer()d.  That causes xen to crash later because the
    linked list of inactive timers gets corrupted, e.g.:
    
    (XEN) Xen call trace:
    (XEN)    [<ffff82c480126256>] set_timer+0x1c2/0x24f
    (XEN)    [<ffff82c48011fbf8>] schedule+0x129/0x5dd
    (XEN)    [<ffff82c480122c1e>] __do_softirq+0x7e/0x89
    (XEN)    [<ffff82c480122c9d>] do_softirq+0x26/0x28
    (XEN)    [<ffff82c480153c85>] idle_loop+0x5a/0x5c
    (XEN)
    (XEN)
    (XEN) ****************************************
    (XEN) Panic on CPU 0:
    (XEN) Assertion 'entry->next->prev == entry' failed at
    /local/scratch/tdeegan/xen-unstable.hg/xen/include:172
    (XEN) ****************************************
    
    The following patch makes sure that the domain destruction path always
    clears up the DPCI state even if !needs_iommu(d).
    
    Signed-off-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
    xen-unstable changeset:   23746:aa54b8175954
    xen-unstable date:        Mon Jul 25 16:41:33 2011 +0100
    
    
changeset:   21524:f09ab04f614e
user:        Keir Fraser <keir@xxxxxxx>
date:        Wed Jul 27 23:12:31 2011 +0100
    
    x86: Replace missing return stmt accidentally removed by 21513:649372e3d46a
    
    Signed-off-by: Keir Fraser <keir@xxxxxxx>
    
    
(qemu changes not included)

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [xen-4.0-testing test] 8662: regressions - trouble: blocked/broken/fail/pass, xen . org <=