* [xen-unstable test] 12889: regressions - FAIL
@ 2012-05-16 7:12 xen.org
2012-05-16 8:34 ` "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL) Ian Campbell
0 siblings, 1 reply; 6+ messages in thread
From: xen.org @ 2012-05-16 7:12 UTC (permalink / raw)
To: xen-devel; +Cc: ian.jackson
flight 12889 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/12889/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail REGR. vs. 12884
test-i386-i386-xl 9 guest-start fail REGR. vs. 12884
test-amd64-amd64-xl-qemuu-win7-amd64 12 guest-localmigrate/x10 fail REGR. vs. 12876
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-qemuu-rhel6hvm-amd 9 guest-start.2 fail like 12884
Tests which did not succeed, but are not blocking:
test-amd64-i386-rhel6hvm-intel 11 leak-check/check fail never pass
test-amd64-i386-qemuu-rhel6hvm-intel 9 guest-start.2 fail never pass
test-i386-i386-xl-qemuu-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-rhel6hvm-amd 11 leak-check/check fail never pass
test-i386-i386-xl-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass
test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass
test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 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
version targeted for testing:
xen 612a24c8c4f9
baseline version:
xen f8279258e3c9
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 pass
test-amd64-i386-xl pass
test-i386-i386-xl fail
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-qemuu-rhel6hvm-amd 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 fail
test-amd64-i386-qemuu-rhel6hvm-intel fail
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 pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv pass
test-amd64-amd64-xl-sedf pass
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-xl-win-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-xl-win fail
test-i386-i386-xl-win 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.
^ permalink raw reply [flat|nested] 6+ messages in thread* "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL)
2012-05-16 7:12 [xen-unstable test] 12889: regressions - FAIL xen.org
@ 2012-05-16 8:34 ` Ian Campbell
2012-05-16 10:24 ` George Dunlap
0 siblings, 1 reply; 6+ messages in thread
From: Ian Campbell @ 2012-05-16 8:34 UTC (permalink / raw)
To: xen.org; +Cc: xen-devel@lists.xensource.com, George.Dunlap
On Wed, 2012-05-16 at 08:12 +0100, xen.org wrote:
> flight 12889 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/12889/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail REGR. vs. 12884
2012-05-16 01:24:41 Z toolstack xl
2012-05-16 01:24:41 Z executing ssh ... root@10.80.249.149 xl pci-list-assignable
command not implemented
I should have anticipated this before committing this change. :-/
I guess we could make the test harness detect which to use, or perhaps
we should just put in a hidden alias command?
Ian.
> test-i386-i386-xl 9 guest-start fail REGR. vs. 12884
> test-amd64-amd64-xl-qemuu-win7-amd64 12 guest-localmigrate/x10 fail REGR. vs. 12876
>
> Regressions which are regarded as allowable (not blocking):
> test-amd64-i386-qemuu-rhel6hvm-amd 9 guest-start.2 fail like 12884
>
> Tests which did not succeed, but are not blocking:
> test-amd64-i386-rhel6hvm-intel 11 leak-check/check fail never pass
> test-amd64-i386-qemuu-rhel6hvm-intel 9 guest-start.2 fail never pass
> test-i386-i386-xl-qemuu-winxpsp3 13 guest-stop fail never pass
> test-amd64-amd64-win 16 leak-check/check fail never pass
> test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
> test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
> test-amd64-i386-rhel6hvm-amd 11 leak-check/check fail never pass
> test-i386-i386-xl-winxpsp3 13 guest-stop fail never pass
> test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass
> test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass
> test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass
> test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass
> test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
> test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
> test-amd64-i386-win 16 leak-check/check fail never pass
> test-amd64-amd64-xl-win 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
>
> version targeted for testing:
> xen 612a24c8c4f9
> baseline version:
> xen f8279258e3c9
>
> 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 pass
> test-amd64-i386-xl pass
> test-i386-i386-xl fail
> test-amd64-i386-rhel6hvm-amd fail
> test-amd64-i386-qemuu-rhel6hvm-amd 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 fail
> test-amd64-i386-qemuu-rhel6hvm-intel fail
> 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 pass
> test-amd64-amd64-pv pass
> test-amd64-i386-pv pass
> test-i386-i386-pv pass
> test-amd64-amd64-xl-sedf pass
> test-amd64-i386-win-vcpus1 fail
> test-amd64-i386-xl-win-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-xl-win fail
> test-i386-i386-xl-win 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.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL)
2012-05-16 8:34 ` "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL) Ian Campbell
@ 2012-05-16 10:24 ` George Dunlap
2012-05-16 10:29 ` Ian Campbell
0 siblings, 1 reply; 6+ messages in thread
From: George Dunlap @ 2012-05-16 10:24 UTC (permalink / raw)
To: Ian Campbell; +Cc: xen-devel@lists.xensource.com, xen.org, George.Dunlap
On Wed, May 16, 2012 at 9:34 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail REGR. vs. 12884
>
> 2012-05-16 01:24:41 Z toolstack xl
> 2012-05-16 01:24:41 Z executing ssh ... root@10.80.249.149 xl pci-list-assignable
> command not implemented
>
> I should have anticipated this before committing this change. :-/
>
> I guess we could make the test harness detect which to use, or perhaps
> we should just put in a hidden alias command?
Why do we need to detect which to use? I pci-list-assignable was
introduced in the 4.2 dev cycle, I believe (which is why I wasn't
worried about changing the name); was it backported to 4.1?
-George
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL)
2012-05-16 10:24 ` George Dunlap
@ 2012-05-16 10:29 ` Ian Campbell
2012-05-17 10:20 ` Ian Jackson
2012-05-17 10:22 ` Ian Jackson
0 siblings, 2 replies; 6+ messages in thread
From: Ian Campbell @ 2012-05-16 10:29 UTC (permalink / raw)
To: George Dunlap; +Cc: George Dunlap, xen-devel@lists.xensource.com, Ian Jackson
On Wed, 2012-05-16 at 11:24 +0100, George Dunlap wrote:
> On Wed, May 16, 2012 at 9:34 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> >> test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail REGR. vs. 12884
> >
> > 2012-05-16 01:24:41 Z toolstack xl
> > 2012-05-16 01:24:41 Z executing ssh ... root@10.80.249.149 xl pci-list-assignable
> > command not implemented
> >
> > I should have anticipated this before committing this change. :-/
> >
> > I guess we could make the test harness detect which to use, or perhaps
> > we should just put in a hidden alias command?
>
> Why do we need to detect which to use?
For the benefit of the bisector when crossing this changeset.
> I pci-list-assignable was
> introduced in the 4.2 dev cycle, I believe (which is why I wasn't
> worried about changing the name); was it backported to 4.1?
>
> -George
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL)
2012-05-16 10:29 ` Ian Campbell
@ 2012-05-17 10:20 ` Ian Jackson
2012-05-17 10:22 ` Ian Jackson
1 sibling, 0 replies; 6+ messages in thread
From: Ian Jackson @ 2012-05-17 10:20 UTC (permalink / raw)
To: Ian Campbell; +Cc: George Dunlap, George Dunlap, xen-devel@lists.xensource.com
Ian Campbell writes ("Re: [Xen-devel] "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL)"):
> On Wed, 2012-05-16 at 11:24 +0100, George Dunlap wrote:
> > On Wed, May 16, 2012 at 9:34 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > > I guess we could make the test harness detect which to use, or perhaps
> > > we should just put in a hidden alias command?
> >
> > Why do we need to detect which to use?
>
> For the benefit of the bisector when crossing this changeset.
>
> > I pci-list-assignable was
> > introduced in the 4.2 dev cycle, I believe (which is why I wasn't
> > worried about changing the name); was it backported to 4.1?
In the interests of expedience, I have simply changed the tester to
use the new name (well, pushed a change to the tester's staging tree
to do so). Bisection will not work if the tester tries to bisect the
pcipt job but I think it's unlikely we'll have another nonobvious
bisectable regression given that the /actual/ test never passes.
Ian.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL)
2012-05-16 10:29 ` Ian Campbell
2012-05-17 10:20 ` Ian Jackson
@ 2012-05-17 10:22 ` Ian Jackson
1 sibling, 0 replies; 6+ messages in thread
From: Ian Jackson @ 2012-05-17 10:22 UTC (permalink / raw)
To: Ian Campbell; +Cc: George Dunlap, George Dunlap, xen-devel@lists.xensource.com
Ian Campbell writes ("Re: [Xen-devel] "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL)"):
> On Wed, 2012-05-16 at 11:24 +0100, George Dunlap wrote:
> > On Wed, May 16, 2012 at 9:34 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > > I guess we could make the test harness detect which to use, or perhaps
> > > we should just put in a hidden alias command?
> >
> > Why do we need to detect which to use?
>
> For the benefit of the bisector when crossing this changeset.
>
> > I pci-list-assignable was
> > introduced in the 4.2 dev cycle, I believe (which is why I wasn't
> > worried about changing the name); was it backported to 4.1?
In the interests of expedience, I have simply changed the tester to
use the new name (well, pushed a change to the tester's staging tree
to do so). Bisection will not work if the tester tries to bisect the
pcipt job but I think it's unlikely we'll have another nonobvious
bisectable regression given that the /actual/ test never passes.
Ian.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-05-17 10:22 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-16 7:12 [xen-unstable test] 12889: regressions - FAIL xen.org
2012-05-16 8:34 ` "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL) Ian Campbell
2012-05-16 10:24 ` George Dunlap
2012-05-16 10:29 ` Ian Campbell
2012-05-17 10:20 ` Ian Jackson
2012-05-17 10:22 ` Ian Jackson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).