Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Xen>
  3. Devel
[xen-4.1-testing test] 14762: regressions - FAIL
ian.jackson at eu
Dec 16, 2012, 8:24 PM
Post #1 of 2 (127 views)
Permalink
flight 14762 xen-4.1-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/14762/

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-rhel6hvm-intel 11 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-rhel6hvm-amd 11 leak-check/check fail REGR. vs. 14679
test-amd64-i386-qemuu-rhel6hvm-amd 11 leak-check/check fail REGR. vs. 14679
test-amd64-i386-xl-multivcpu 18 leak-check/check fail REGR. vs. 14679
test-amd64-i386-qemut-rhel6hvm-intel 11 leak-check/check fail REGR. vs. 14679
test-amd64-i386-qemuu-rhel6hvm-intel 11 leak-check/check fail REGR. vs. 14679

Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-sedf 9 guest-start fail pass in 14756
test-i386-i386-xl-qemut-winxpsp3 7 windows-install fail in 14756 pass in 14762

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-pin 18 leak-check/check fail REGR. vs. 14679
test-amd64-amd64-xl-sedf 11 guest-localmigrate fail in 14756 like 14679

Tests which did not succeed, but are not blocking:
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop fail never pass
test-i386-i386-xl-qemut-win 13 guest-stop fail never pass
test-i386-i386-xl-win 13 guest-stop fail never pass
test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail never pass
test-amd64-i386-xl-qemut-win-vcpus1 13 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-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-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-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-amd64-xl-winxpsp3 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-i386-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-qemut-win 13 guest-stop fail never pass
test-i386-i386-qemut-win 16 leak-check/check 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-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-amd64-amd64-xl-win 13 guest-stop fail never pass
test-i386-i386-xl-qemuu-winxpsp3 13 guest-stop fail never pass
test-i386-i386-xl-qemut-winxpsp3 13 guest-stop fail 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)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Re: [xen-4.1-testing test] 14762: regressions - FAIL [ In reply to ]
Ian.Campbell at citrix
Dec 17, 2012, 2:25 AM
Post #2 of 2 (122 views)
Permalink
On Mon, 2012-12-17 at 04:24 +0000, xen.org wrote:
> flight 14762 xen-4.1-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/14762/
>
> 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-rhel6hvm-intel 11 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-rhel6hvm-amd 11 leak-check/check fail REGR. vs. 14679
> test-amd64-i386-qemuu-rhel6hvm-amd 11 leak-check/check fail REGR. vs. 14679
> test-amd64-i386-xl-multivcpu 18 leak-check/check fail REGR. vs. 14679
> test-amd64-i386-qemut-rhel6hvm-intel 11 leak-check/check fail REGR. vs. 14679
> test-amd64-i386-qemuu-rhel6hvm-intel 11 leak-check/check fail REGR. vs. 14679
[...]

http://www.chiark.greenend.org.uk/~xensrcts/logs/14706/test-amd64-amd64-xl/18.ts-leak-check.log
shows a load of leaked xenstore paths relating to the console. The
bisector has fingered the first one (23428:93e17b0cd035) as having
caused it.

Given that we are at 4.1.4-rc2 unless we can fix this today (or by
tomorrow) we should revert. Possibly we should even just revert and try
again for 4.1.5.

Perhaps we should leave the both the libxl__device_destroy_tapdisk and
xs_rm in libxl__device_destroy? The xs_rm is harmless in the case where
libxl__device_destroy_tapdisk has done something and useful when it has
not.

The call to libxl__device_destroy_tapdisk in libxl__devices_destroy from
the second patch also looks entirely to me -- the function loops over
devices and yet calls that function only only for the last one (which
happens to be a console). I think this is a mismerge on the backport
23427:255a0b6a8104 (to unstable) makes this change to
libxl__device_destroy with very similar context to the change to
libxl__devices_destroy in 23427:255a0b6a8104 (to 4.1-testing).

Ian.

> ------------------------------------------------------------
> 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)
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal