thr3ads.net - Xen devel - [xen-4.1-testing test] 14689: regressions

If this information is useful, please help other people find it:
Share via:

xen.org

2012-Dec-14 11:45 UTC

[xen-4.1-testing test] 14689: regressions - FAIL

flight 14689 xen-4.1-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/14689/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-qemut-rhel6hvm-amd 11 leak-check/check    fail REGR. vs. 14679
 test-amd64-amd64-xl          18 leak-check/check          fail REGR. vs. 14679
 test-amd64-i386-qemuu-rhel6hvm-intel 11 leak-check/check  fail REGR. vs. 14679
 test-amd64-i386-rhel6hvm-intel 11 leak-check/check        fail REGR. vs. 14679
 test-amd64-i386-xl-multivcpu 18 leak-check/check          fail REGR. vs. 14679
 test-amd64-i386-xl           18 leak-check/check          fail REGR. vs. 14679
 test-i386-i386-xl            18 leak-check/check          fail REGR. vs. 14679
 test-amd64-i386-xl-credit2   18 leak-check/check          fail REGR. vs. 14679
 test-amd64-i386-qemuu-rhel6hvm-amd 11 leak-check/check    fail REGR. vs. 14679
 test-amd64-i386-rhel6hvm-amd 11 leak-check/check          fail REGR. vs. 14679
 test-amd64-i386-qemut-rhel6hvm-intel 11 leak-check/check  fail REGR. vs. 14679

Tests which are failing intermittently (not blocking):
 test-amd64-i386-win           7 windows-install             fail pass in 14684
 test-amd64-i386-xl-credit2   10 guest-saverestore  fail in 14684 pass in 14689
 test-i386-i386-xl-win    12 guest-localmigrate/x10 fail in 14684 pass in 14689

Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-xl-pcipt-intel  8 debian-fixup                fail like 14679
 test-amd64-amd64-xl-sedf     18 leak-check/check         fail blocked in 14679
 test-amd64-amd64-xl-sedf-pin 18 leak-check/check          fail REGR. vs. 14679

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 test-i386-i386-xl-qemut-win  13 guest-stop                   fail   never pass
 test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop              fail never pass
 test-amd64-i386-xl-qemut-win-vcpus1 13 guest-stop              fail never pass
 test-i386-i386-xl-win        13 guest-stop                   fail   never pass
 test-i386-i386-win           16 leak-check/check             fail   never pass
 test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check        fail never pass
 test-amd64-amd64-xl-win7-amd64 13 guest-stop                   fail never pass
 test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop             fail never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop             fail never pass
 test-amd64-i386-qemut-win-vcpus1 16 leak-check/check           fail never pass
 test-amd64-amd64-xl-winxpsp3 13 guest-stop                   fail   never pass
 test-amd64-i386-win-vcpus1   16 leak-check/check             fail   never pass
 test-amd64-i386-xl-win7-amd64 13 guest-stop                   fail  never pass
 test-amd64-i386-xl-win-vcpus1 13 guest-stop                   fail  never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop               fail never pass
 test-amd64-i386-xend-winxpsp3 16 leak-check/check             fail  never pass
 test-amd64-amd64-xl-qemut-win 13 guest-stop                   fail  never pass
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop         fail never pass
 test-amd64-amd64-qemut-win   16 leak-check/check             fail   never pass
 test-i386-i386-qemut-win     16 leak-check/check             fail   never pass
 test-amd64-i386-qemut-win    16 leak-check/check             fail   never pass
 test-i386-i386-xl-winxpsp3   13 guest-stop                   fail   never pass
 test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop               fail never pass
 test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop               fail never pass
 test-i386-i386-xl-qemut-winxpsp3 13 guest-stop                 fail never pass
 test-i386-i386-xl-qemuu-winxpsp3 13 guest-stop                 fail never pass
 test-amd64-amd64-xl-win      13 guest-stop                   fail   never pass
 test-amd64-i386-win          16 leak-check/check      fail in 14684 never pass

version targeted for testing:
 xen                  93e17b0cd035
baseline version:
 xen                  255a0b6a8104

------------------------------------------------------------
People who touched revisions under test:
  Greg Wettstein <greg@enjellic.com>
  Ian Campbell <ian.campbell@citrix.com>
  Ian Jackson <ian.jackson@eu.citrix.com>
------------------------------------------------------------

jobs:
 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                                           fail    
 test-i386-i386-xl                                            fail    
 test-amd64-i386-rhel6hvm-amd                                 fail    
 test-amd64-i386-qemut-rhel6hvm-amd                           fail    
 test-amd64-i386-qemuu-rhel6hvm-amd                           fail    
 test-amd64-amd64-xl-qemut-win7-amd64                         fail    
 test-amd64-i386-xl-qemut-win7-amd64                          fail    
 test-amd64-amd64-xl-qemuu-win7-amd64                         fail    
 test-amd64-amd64-xl-win7-amd64                               fail    
 test-amd64-i386-xl-win7-amd64                                fail    
 test-amd64-i386-xl-credit2                                   fail    
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-i386-rhel6hvm-intel                               fail    
 test-amd64-i386-qemut-rhel6hvm-intel                         fail    
 test-amd64-i386-qemuu-rhel6hvm-intel                         fail    
 test-amd64-i386-xl-multivcpu                                 fail    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-i386-i386-pair                                          pass    
 test-amd64-amd64-xl-sedf-pin                                 fail    
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           pass    
 test-i386-i386-pv                                            pass    
 test-amd64-amd64-xl-sedf                                     fail    
 test-amd64-i386-win-vcpus1                                   fail    
 test-amd64-i386-qemut-win-vcpus1                             fail    
 test-amd64-i386-xl-qemut-win-vcpus1                          fail    
 test-amd64-i386-xl-win-vcpus1                                fail    
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     fail    
 test-amd64-i386-xl-winxpsp3-vcpus1                           fail    
 test-amd64-amd64-win                                         fail    
 test-amd64-i386-win                                          fail    
 test-i386-i386-win                                           fail    
 test-amd64-amd64-qemut-win                                   fail    
 test-amd64-i386-qemut-win                                    fail    
 test-i386-i386-qemut-win                                     fail    
 test-amd64-amd64-xl-qemut-win                                fail    
 test-i386-i386-xl-qemut-win                                  fail    
 test-amd64-amd64-xl-win                                      fail    
 test-i386-i386-xl-win                                        fail    
 test-amd64-i386-xend-qemut-winxpsp3                          fail    
 test-amd64-amd64-xl-qemut-winxpsp3                           fail    
 test-i386-i386-xl-qemut-winxpsp3                             fail    
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail    
 test-i386-i386-xl-qemuu-winxpsp3                             fail    
 test-amd64-i386-xend-winxpsp3                                fail    
 test-amd64-amd64-xl-winxpsp3                                 fail    
 test-i386-i386-xl-winxpsp3                                   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:   23428:93e17b0cd035
tag:         tip
user:        Greg Wettstein <greg@enjellic.com>
date:        Thu Dec 13 14:35:58 2012 +0000
    
    libxl: avoid blktap2 deadlock on cleanup
    
    Establishes correct cleanup behavior for blktap devices.  This patch
    implements the release of the backend device before calling for
    the destruction of the userspace component of the blktap device.
    
    Without this patch the kernel xen-blkback driver deadlocks with
    the blktap2 user control plane until the IPC channel is terminated by the
    timeout on the select() call.  This results in a noticeable delay
    in the termination of the guest and causes the blktap minor
    number which had been allocated to be orphaned.
    
    Signed-off-by: Greg Wettstein <greg@enjellic.com>
    Acked-by: Ian Campbell <ian.campbell@citrix.com>
    Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
    Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
    
    
changeset:   23427:255a0b6a8104
user:        Ian Jackson <Ian.Jackson@eu.citrix.com>
date:        Wed Dec 12 17:41:15 2012 +0000
    
    From: Ian Campbell <ian.campbell@citrix.com>
    
    libxl: attempt to cleanup tapdisk processes on disk backend destroy.
    
    This patch properly terminates the tapdisk2 process(es) started
    to service a virtual block device.
    
    Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
    Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
    
    xen-unstable changeset: 23883:7998217630e2
    xen-unstable date: Wed Sep 28 16:42:11 2011 +0100
    Signed-off-by: Greg Wettstein <greg@enjellic.com>
    Backport-requested-by: Greg Wettstein <greg@enjellic.com>
    Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
    
    
(qemu changes not included)

Jan Beulich

2012-Dec-17 10:22 UTC

head link

Re: [xen-4.1-testing test] 14689: regressions - FAIL

>>> On 14.12.12 at 12:45, xen.org <ian.jackson@eu.citrix.com>
wrote:
> flight 14689 xen-4.1-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/14689/ 
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-qemut-rhel6hvm-amd 11 leak-check/check    fail REGR. vs.
14679
>  test-amd64-amd64-xl          18 leak-check/check          fail REGR. vs.
14679
>  test-amd64-i386-qemuu-rhel6hvm-intel 11 leak-check/check  fail REGR. vs.
14679
>  test-amd64-i386-rhel6hvm-intel 11 leak-check/check        fail REGR. vs.
14679
>  test-amd64-i386-xl-multivcpu 18 leak-check/check          fail REGR. vs.
14679
>  test-amd64-i386-xl           18 leak-check/check          fail REGR. vs.
14679
>  test-i386-i386-xl            18 leak-check/check          fail REGR. vs.
14679
>  test-amd64-i386-xl-credit2   18 leak-check/check          fail REGR. vs.
14679
>  test-amd64-i386-qemuu-rhel6hvm-amd 11 leak-check/check    fail REGR. vs.
14679
>  test-amd64-i386-rhel6hvm-amd 11 leak-check/check          fail REGR. vs.
14679
>  test-amd64-i386-qemut-rhel6hvm-intel 11 leak-check/check  fail REGR. vs.
14679
So this is what really should not have happened past the
intended-to-be-final RC.
> ------------------------------------------------------------
> changeset:   23428:93e17b0cd035
> tag:         tip
> user:        Greg Wettstein <greg@enjellic.com>
> date:        Thu Dec 13 14:35:58 2012 +0000
>     
>     libxl: avoid blktap2 deadlock on cleanup
>     
>     Establishes correct cleanup behavior for blktap devices.  This patch
>     implements the release of the backend device before calling for
>     the destruction of the userspace component of the blktap device.
>     
>     Without this patch the kernel xen-blkback driver deadlocks with
>     the blktap2 user control plane until the IPC channel is terminated by 
> the
>     timeout on the select() call.  This results in a noticeable delay
>     in the termination of the guest and causes the blktap minor
>     number which had been allocated to be orphaned.
>     
>     Signed-off-by: Greg Wettstein <greg@enjellic.com>
>     Acked-by: Ian Campbell <ian.campbell@citrix.com>
>     Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
>     Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
How important is this change really to the 4.1 tree? I''d obviously
favor outright reverting it at this point (my understanding being
that the removal of the call to xs_rm() from libxl__device_destroy()
affected more than just tapdisk backends, which I guess was
assumed to be the case because of its neighboring with the call
to libxl__device_destroy_tapdisk()). Would that get the tree into
worse state that 4.1.3 was in?

Jan

Ian Jackson

2012-Dec-17 11:52 UTC

head link

Re: [xen-4.1-testing test] 14689: regressions - FAIL

Jan Beulich writes ("Re: [Xen-devel] [xen-4.1-testing test] 14689:
regressions - FAIL"):> So this is what really should not have happened past the
> intended-to-be-final RC.
Sorry about that.
> How important is this change really to the 4.1 tree? I''d obviously
> favor outright reverting it at this point (my understanding being
> that the removal of the call to xs_rm() from libxl__device_destroy()
> affected more than just tapdisk backends, which I guess was
> assumed to be the case because of its neighboring with the call
> to libxl__device_destroy_tapdisk()). Would that get the tree into
> worse state that 4.1.3 was in?
I think reverting it right now is the right thing to do and I will do
that.  We can then think about what to do next.

Ian.

Ian Jackson

2012-Dec-17 11:55 UTC

head link

Re: [xen-4.1-testing test] 14689: regressions - FAIL

Ian Jackson writes ("Re: [Xen-devel] [xen-4.1-testing test] 14689:
regressions - FAIL"):> Jan Beulich writes ("Re: [Xen-devel] [xen-4.1-testing test] 14689:
regressions - FAIL"):
> > So this is what really should not have happened past the
> > intended-to-be-final RC.
> 
> Sorry about that.
> 
> > How important is this change really to the 4.1 tree? I''d
obviously
> > favor outright reverting it at this point (my understanding being
> > that the removal of the call to xs_rm() from libxl__device_destroy()
> > affected more than just tapdisk backends, which I guess was
> > assumed to be the case because of its neighboring with the call
> > to libxl__device_destroy_tapdisk()). Would that get the tree into
> > worse state that 4.1.3 was in?
> 
> I think reverting it right now is the right thing to do and I will do
> that.  We can then think about what to do next.
Now done.

Ian.

Xen devel - Dec 2012 - [xen-4.1-testing test] 14689: regressions - FAIL

[xen-4.1-testing test] 14689: regressions - FAIL

Re: [xen-4.1-testing test] 14689: regressions - FAIL

Re: [xen-4.1-testing test] 14689: regressions - FAIL

Re: [xen-4.1-testing test] 14689: regressions - FAIL