* [xen-unstable test] 25858: regressions - FAIL
@ 2014-04-12 6:15 xen.org
2014-04-14 10:03 ` Jan Beulich
0 siblings, 1 reply; 5+ messages in thread
From: xen.org @ 2014-04-12 6:15 UTC (permalink / raw)
To: xen-devel; +Cc: ian.jackson
[-- Attachment #1: Type: text/plain, Size: 7044 bytes --]
flight 25858 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/25858/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386 4 xen-build fail REGR. vs. 25819
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-sedf-pin 15 guest-localmigrate/x10 fail REGR. vs. 25819
Tests which did not succeed, but are not blocking:
test-amd64-i386-rhel6hvm-amd 1 xen-build-check(1) blocked n/a
test-amd64-i386-qemut-rhel6hvm-amd 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-i386-qemut-rhel6hvm-intel 1 xen-build-check(1) blocked n/a
test-amd64-i386-qemuu-rhel6hvm-intel 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl 1 xen-build-check(1) blocked n/a
test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-amd64-i386-freebsd10-amd64 1 xen-build-check(1) blocked n/a
test-amd64-i386-freebsd10-i386 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-winxpsp3 1 xen-build-check(1) blocked n/a
test-amd64-i386-qemuu-rhel6hvm-amd 1 xen-build-check(1) blocked n/a
test-amd64-i386-pair 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-stop fail never pass
test-amd64-i386-xl-win7-amd64 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-winxpsp3-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-winxpsp3 14 guest-stop fail never pass
test-amd64-amd64-xl-winxpsp3 14 guest-stop fail never pass
test-amd64-i386-xl-winxpsp3 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-qemut-winxpsp3 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-win7-amd64 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-win7-amd64 14 guest-stop fail never pass
test-amd64-amd64-xl-qemut-winxpsp3 14 guest-stop fail never pass
test-amd64-i386-xl-qemut-win7-amd64 1 xen-build-check(1) blocked n/a
test-armhf-armhf-xl 10 migrate-support-check fail never pass
test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop fail never pass
version targeted for testing:
xen 29ded52bd4c47a2d3b11afe1f96844b6dfdb23e1
baseline version:
xen d2b4c27c0718f27deba00a16317a8ba04c1a2cb7
------------------------------------------------------------
People who touched revisions under test:
Bob Liu <bob.liu@oracle.com>
Christoph Egger <chegger@amazon.de>
Daniel De Graaf <dgdegra@tycho.nsa.gov>
Don Slutz <dslutz@verizon.com>
George Dunlap <george.dunlap@eu.citrix.com>
Ian Campbell <ian.campbell@citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
Jan Beulich <jbeulich@suse.com>
Julien Grall <julien.grall@linaro.org>
Keir Fraser <keir@xen.org>
Kevin Tian <kevin.tian@intel.com>
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Liu Jinsong <jinsong.liu@alibaba-inc.com>
Olaf Hering <olaf@aepfle.de>
Roger Pau Monné <roger.pau@citrix.com>
Wei Liu <wei.liu2@citrix.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf pass
build-i386 fail
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-armhf-armhf-xl pass
test-amd64-i386-xl blocked
test-amd64-i386-rhel6hvm-amd blocked
test-amd64-i386-qemut-rhel6hvm-amd blocked
test-amd64-i386-qemuu-rhel6hvm-amd blocked
test-amd64-i386-freebsd10-amd64 blocked
test-amd64-amd64-xl-qemut-win7-amd64 fail
test-amd64-i386-xl-qemut-win7-amd64 blocked
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 blocked
test-amd64-amd64-xl-win7-amd64 fail
test-amd64-i386-xl-win7-amd64 blocked
test-amd64-i386-xl-credit2 blocked
test-amd64-i386-freebsd10-i386 blocked
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel blocked
test-amd64-i386-qemut-rhel6hvm-intel blocked
test-amd64-i386-qemuu-rhel6hvm-intel blocked
test-amd64-i386-xl-multivcpu blocked
test-amd64-amd64-pair pass
test-amd64-i386-pair blocked
test-amd64-amd64-xl-sedf-pin fail
test-amd64-amd64-xl-sedf pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 blocked
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 blocked
test-amd64-i386-xl-winxpsp3-vcpus1 blocked
test-amd64-amd64-xl-qemut-winxpsp3 fail
test-amd64-i386-xl-qemut-winxpsp3 blocked
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-amd64-i386-xl-qemuu-winxpsp3 blocked
test-amd64-amd64-xl-winxpsp3 fail
test-amd64-i386-xl-winxpsp3 blocked
------------------------------------------------------------
sg-report-flight on osstest.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.
(No revision log; it would be 798 lines long.)
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xen-unstable test] 25858: regressions - FAIL
2014-04-12 6:15 [xen-unstable test] 25858: regressions - FAIL xen.org
@ 2014-04-14 10:03 ` Jan Beulich
2014-04-14 10:26 ` Ian Campbell
2014-04-14 10:55 ` Ian Jackson
0 siblings, 2 replies; 5+ messages in thread
From: Jan Beulich @ 2014-04-14 10:03 UTC (permalink / raw)
To: xen-devel; +Cc: Ian Campbell, ian.jackson
>>> On 12.04.14 at 08:15, <Ian.Jackson@eu.citrix.com> wrote:
> flight 25858 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/25858/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-i386 4 xen-build fail REGR. vs. 25819
So it's not clear to me whether this
+ perl -i.bak -pe '
next unless m/^exit 0/;
print "setopt CONFIG_HIGHPTE n\n" or die $!;
print "setopt CONFIG_TUN y\n" or die $!;
print "setopt CONFIG_BLK_DEV_NBD m\n" or die $!;
print "setopt CONFIG_DEBUG_INFO y\n" or die $!;
' buildconfigs/enable-xen-config
Can't open buildconfigs/enable-xen-config: No such file or directory.
is causing the failure, or whether it's "only" again suffering from the
timeout issue:
failure (trapped): status (timed out) at Osstest/TestSupport.pm line 385.
I would have thought that at least on of the five flights that were run
over the weekend should have gotten away without hitting the timeout,
but of course I don't know how busy the build systems were.
Jan
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xen-unstable test] 25858: regressions - FAIL
2014-04-14 10:03 ` Jan Beulich
@ 2014-04-14 10:26 ` Ian Campbell
2014-04-14 10:55 ` Ian Jackson
1 sibling, 0 replies; 5+ messages in thread
From: Ian Campbell @ 2014-04-14 10:26 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel, ian.jackson
On Mon, 2014-04-14 at 11:03 +0100, Jan Beulich wrote:
> >>> On 12.04.14 at 08:15, <Ian.Jackson@eu.citrix.com> wrote:
> > flight 25858 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/25858/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > build-i386 4 xen-build fail REGR. vs. 25819
>
> So it's not clear to me whether this
>
> + perl -i.bak -pe '
> next unless m/^exit 0/;
> print "setopt CONFIG_HIGHPTE n\n" or die $!;
> print "setopt CONFIG_TUN y\n" or die $!;
> print "setopt CONFIG_BLK_DEV_NBD m\n" or die $!;
> print "setopt CONFIG_DEBUG_INFO y\n" or die $!;
> ' buildconfigs/enable-xen-config
> Can't open buildconfigs/enable-xen-config: No such file or directory.
>
> is causing the failure,
It really should, but it doesn't appear to be, the test script seems to
continue.
This code should be redundant since osstest.git commit c1fba9810435
"import enable-xen-config from xen.git, use for ts-kernel-build" and is
just wrong since xen.git 40305629dc48 "build: remove Linux kernel build
integration."
And the latter seems to be stuck in staging, so perhaps it is that
change causing the problem then, but more likely it is related to some
networking issues the test controller had over the w/e.
I'll prep a patch to nuke this unneccssary code.
Ian.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xen-unstable test] 25858: regressions - FAIL
2014-04-14 10:03 ` Jan Beulich
2014-04-14 10:26 ` Ian Campbell
@ 2014-04-14 10:55 ` Ian Jackson
2014-04-14 11:12 ` Ian Campbell
1 sibling, 1 reply; 5+ messages in thread
From: Ian Jackson @ 2014-04-14 10:55 UTC (permalink / raw)
To: Jan Beulich; +Cc: Ian Campbell, xen-devel
Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 25858: regressions - FAIL"):
> On 12.04.14 at 08:15, <Ian.Jackson@eu.citrix.com> wrote:
> > flight 25858 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/25858/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > build-i386 4 xen-build fail REGR. vs. 25819
>
> So it's not clear to me whether this
>
> + perl -i.bak -pe '
> next unless m/^exit 0/;
> print "setopt CONFIG_HIGHPTE n\n" or die $!;
> print "setopt CONFIG_TUN y\n" or die $!;
> print "setopt CONFIG_BLK_DEV_NBD m\n" or die $!;
> print "setopt CONFIG_DEBUG_INFO y\n" or die $!;
> ' buildconfigs/enable-xen-config
> Can't open buildconfigs/enable-xen-config: No such file or directory.
mariner:~/junk> perl -i.bak -pe '' nonexistent
Can't open nonexistent: No such file or directory.
mariner:~/junk> echo $?
0
mariner:~/junk>
OMG WTF BBQ
I'm not sure what to do about this. I mean, the buildconfigs editing
thing should probably go, but I'm wondering if we have to go through
and remove all uses of perl -i.
> is causing the failure, or whether it's "only" again suffering from the
> timeout issue:
>
> failure (trapped): status (timed out) at Osstest/TestSupport.pm line 385.
>
> I would have thought that at least on of the five flights that were run
> over the weekend should have gotten away without hitting the timeout,
> but of course I don't know how busy the build systems were.
There seem to have been problems with the osstest vm's networking
which I guess might have made things slow before they stopped
altogether.
Ian.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xen-unstable test] 25858: regressions - FAIL
2014-04-14 10:55 ` Ian Jackson
@ 2014-04-14 11:12 ` Ian Campbell
0 siblings, 0 replies; 5+ messages in thread
From: Ian Campbell @ 2014-04-14 11:12 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel, Jan Beulich
On Mon, 2014-04-14 at 11:55 +0100, Ian Jackson wrote:
> Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 25858: regressions - FAIL"):
> > On 12.04.14 at 08:15, <Ian.Jackson@eu.citrix.com> wrote:
> > > flight 25858 xen-unstable real [real]
> > > http://www.chiark.greenend.org.uk/~xensrcts/logs/25858/
> > >
> > > Regressions :-(
> > >
> > > Tests which did not succeed and are blocking,
> > > including tests which could not be run:
> > > build-i386 4 xen-build fail REGR. vs. 25819
> >
> > So it's not clear to me whether this
> >
> > + perl -i.bak -pe '
> > next unless m/^exit 0/;
> > print "setopt CONFIG_HIGHPTE n\n" or die $!;
> > print "setopt CONFIG_TUN y\n" or die $!;
> > print "setopt CONFIG_BLK_DEV_NBD m\n" or die $!;
> > print "setopt CONFIG_DEBUG_INFO y\n" or die $!;
> > ' buildconfigs/enable-xen-config
> > Can't open buildconfigs/enable-xen-config: No such file or directory.
>
> mariner:~/junk> perl -i.bak -pe '' nonexistent
> Can't open nonexistent: No such file or directory.
> mariner:~/junk> echo $?
> 0
> mariner:~/junk>
>
> OMG WTF BBQ
Indeed.
> I'm not sure what to do about this. I mean, the buildconfigs editing
> thing should probably go, but I'm wondering if we have to go through
> and remove all uses of perl -i.
Is it only -i or is -e (or -p)? I think it's e or p.
$ perl -pe '' /tmp/foo ; echo $?Can't open /tmp/foo: No such file or
directory.
0
$
Ian.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-04-14 11:12 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-12 6:15 [xen-unstable test] 25858: regressions - FAIL xen.org
2014-04-14 10:03 ` Jan Beulich
2014-04-14 10:26 ` Ian Campbell
2014-04-14 10:55 ` Ian Jackson
2014-04-14 11:12 ` Ian Campbell
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.