flight 16690 xen-4.2-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/16690/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-oldkern 4 xen-build fail REGR. vs. 16228
build-i386-oldkern 4 xen-build fail REGR. vs. 16228
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-sedf-pin 10 guest-saverestore fail REGR. vs. 16228
test-amd64-amd64-xl-sedf 11 guest-localmigrate fail REGR. vs. 16228
Tests which did not succeed, but are not blocking:
build-armhf 4 xen-build fail never pass
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop fail never pass
test-i386-i386-xl-qemuu-winxpsp3 9 guest-localmigrate fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 9 guest-localmigrate fail never pass
test-amd64-amd64-xl-qemut-win 13 guest-stop fail never pass
test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-qemut-win 16 leak-check/check fail never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-i386-i386-xl-winxpsp3 13 guest-stop fail never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xl-qemut-win-vcpus1 13 guest-stop fail never pass
test-amd64-i386-qemut-win-vcpus1 16 leak-check/check fail never pass
test-i386-i386-xl-qemut-win 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 9 guest-localmigrate fail never pass
test-amd64-i386-qemut-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-i386-i386-xl-qemut-winxpsp3 13 guest-stop fail never pass
test-i386-i386-qemut-win 16 leak-check/check 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-amd64-xl-qemut-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-win 16 leak-check/check fail never pass
version targeted for testing:
xen b5445b141f6809dd4fa3ee4a11926eab6fc1f50c
baseline version:
xen 61401264eb00fae4ee4efc8e9a5067449283207b
------------------------------------------------------------
People who touched revisions under test:
Jan Beulich <jbeulich@suse.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf fail
build-i386 pass
build-amd64-oldkern fail
build-i386-oldkern fail
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-i386-rhel6hvm-amd pass
test-amd64-i386-qemut-rhel6hvm-amd pass
test-amd64-i386-qemuu-rhel6hvm-amd pass
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 pass
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel pass
test-amd64-i386-qemut-rhel6hvm-intel pass
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-i386-xl-multivcpu pass
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.
------------------------------------------------------------
commit b5445b141f6809dd4fa3ee4a11926eab6fc1f50c
Author: Jan Beulich <jbeulich@suse.com>
Date: Mon Feb 25 13:20:22 2013 +0100
x86_32: fix acpi_dmar_init()
map_pages_to_xen() can''t be used here on x86_32, need to use up to
2
newly introduced fixmap entries for this instead.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
(qemu changes not included)
>>> On 26.02.13 at 12:11, xen.org <ian.jackson@eu.citrix.com> wrote: > flight 16690 xen-4.2-testing real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/16690/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > build-amd64-oldkern 4 xen-build fail REGR. vs. 16228 > build-i386-oldkern 4 xen-build fail REGR. vs. 16228The kernel build didn''t even start when these failed, yet the real reason for the failure also isn''t clear to me. Trying to glue together the matching pieces, I think is goes like this: make[2]: Entering directory `/home/osstest/build.16690.build-i386-oldkern/xen-unstable'' set -e ; \ if [ ! -e linux-2.6.18-xen.hg/.hg ] ; then \ __repo=http://xenbits.xen.org/linux-2.6.18-xen.hg ; \ if [ -d ${__repo} ] ; then \ echo "Linking ${__repo} to linux-2.6.18-xen.hg." ; \ ln -s ${__repo} linux-2.6.18-xen.hg ; \ else \ echo "Cloning ${__repo} to linux-2.6.18-xen.hg." ; \ hg clone ${__repo#file://} linux-2.6.18-xen.hg ; \ fi ; \ else \ __parent=$(hg -R linux-2.6.18-xen.hg path default) ; \ echo "Pulling changes from ${__parent} into linux-2.6.18-xen.hg." ; \ hg -R linux-2.6.18-xen.hg pull ${__parent} ; \ fi Cloning http://xenbits.xen.org/linux-2.6.18-xen.hg to linux-2.6.18-xen.hg. ... requesting all changes adding changesets adding manifests adding file changes transaction abort! rollback completed abort: Connection reset by peer make[2]: Leaving directory `/home/osstest/build.16690.build-i386-oldkern/xen-unstable'' make[2]: *** [linux-2.6.18-xen.hg/.valid-src] Error 255 make[1]: *** [linux-2.6-xen-install] Error 2 make: *** [install-kernels] Error 1 make[1]: Leaving directory `/home/osstest/build.16690.build-i386-oldkern/xen-unstable'' The odd thing being that neither 4.1 nor master had similar problems in their tests. Do we simply need to wait for another run? Jan
Jan Beulich writes ("Re: [Xen-devel] [xen-4.2-testing test] 16690:
regressions - FAIL"):> The kernel build didn''t even start when these failed, yet the
> real reason for the failure also isn''t clear to me. Trying to glue
> together the matching pieces, I think is goes like this:
>
...> Cloning http://xenbits.xen.org/linux-2.6.18-xen.hg to linux-2.6.18-xen.hg.
> ...
> requesting all changes
> adding changesets
> adding manifests
> adding file changes
> transaction abort!
> rollback completed
> abort: Connection reset by peer
> make[2]: Leaving directory
`/home/osstest/build.16690.build-i386-oldkern/xen-unstable''
> make[2]: *** [linux-2.6.18-xen.hg/.valid-src] Error 255
> make[1]: *** [linux-2.6-xen-install] Error 2
> make: *** [install-kernels] Error 1
> make[1]: Leaving directory
`/home/osstest/build.16690.build-i386-oldkern/xen-unstable''
>
> The odd thing being that neither 4.1 nor master had similar
> problems in their tests. Do we simply need to wait for another
> run?
This is indeed odd. I''m hoping it''s a network glitch and that
hg is
simply printing its messages in a funny order. In which case the next
run ought to work.
Ian.