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.1-testing test] 8273: regressions - trouble: blocked/

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [xen-4.1-testing test] 8273: regressions - trouble: blocked/broken/fail/pass
From: xen.org <ian.jackson@xxxxxxxxxxxxx>
Date: Mon, 25 Jul 2011 19:28:15 +0100
Cc: ian.jackson@xxxxxxxxxxxxx
Delivery-date: Mon, 25 Jul 2011 11:29:26 -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 8273 xen-4.1-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/8273/

Regressions :-(

Tests which did not succeed and are blocking:
 build-amd64                   4 xen-build                  fail REGR. vs. 8257
 build-amd64-pvops             4 kernel-build               fail REGR. vs. 8257
 build-amd64-oldkern           4 xen-build                  fail REGR. vs. 8257
 test-i386-i386-win            3 host-install(3)              broken

Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
 test-amd64-amd64-xl-pcipt-intel  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl            1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-pair          1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-rhel6hvm-intel  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-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-multivcpu  1 xen-build-check(1)           blocked  n/a
 test-amd64-amd64-xl           1 xen-build-check(1)           blocked  n/a
 test-amd64-amd64-pv           1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-win           1 xen-build-check(1)           blocked  n/a
 test-amd64-amd64-xl-win       1 xen-build-check(1)           blocked  n/a
 test-i386-i386-xl-win        13 guest-stop                   fail   never pass
 test-amd64-amd64-pair         1 xen-build-check(1)           blocked  n/a
 test-amd64-amd64-win          1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl-win-vcpus1  1 xen-build-check(1)           blocked  n/a

version targeted for testing:
 xen                  cb22fa57ff25
baseline version:
 xen                  4d5c76248de3

------------------------------------------------------------
People who touched revisions under test:
  Roger Pau Monne <roger.pau@xxxxxxxxxxxxx>
  Tim Deegan <Tim.Deegan@xxxxxxxxxx>
------------------------------------------------------------

jobs:
 build-amd64                                                  fail    
 build-i386                                                   pass    
 build-amd64-oldkern                                          fail    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            fail    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl                                          blocked 
 test-amd64-i386-xl                                           blocked 
 test-i386-i386-xl                                            pass    
 test-amd64-i386-rhel6hvm-amd                                 blocked 
 test-amd64-i386-xl-credit2                                   blocked 
 test-amd64-amd64-xl-pcipt-intel                              blocked 
 test-amd64-i386-rhel6hvm-intel                               blocked 
 test-amd64-i386-xl-multivcpu                                 blocked 
 test-amd64-amd64-pair                                        blocked 
 test-amd64-i386-pair                                         blocked 
 test-i386-i386-pair                                          pass    
 test-amd64-amd64-pv                                          blocked 
 test-amd64-i386-pv                                           blocked 
 test-i386-i386-pv                                            pass    
 test-amd64-i386-win-vcpus1                                   blocked 
 test-amd64-i386-xl-win-vcpus1                                blocked 
 test-amd64-amd64-win                                         blocked 
 test-amd64-i386-win                                          blocked 
 test-i386-i386-win                                           broken  
 test-amd64-amd64-xl-win                                      blocked 
 test-i386-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:   23111:cb22fa57ff25
tag:         tip
user:        Tim Deegan <Tim.Deegan@xxxxxxxxxx>
date:        Mon Jul 25 16:48:39 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:   23110:4d5c76248de3
user:        Roger Pau Monne <roger.pau@xxxxxxxxxxxxx>
date:        Sat Jul 23 09:01:25 2011 +0100
    
    xend: remove PCI device listing from NetBSD, since it's Linux
    specific code.
    
    Signed-off-by: Roger Pau Monne <roger.pau@xxxxxxxxxxxxx>
    xen-unstable changeset:   23738:88847c424eec
    xen-unstable date:        Sat Jul 23 08:58:37 2011 +0100
    
    
(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.1-testing test] 8273: regressions - trouble: blocked/broken/fail/pass, xen . org <=