flight 12353 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/12353/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
build-i386-pvops 4 kernel-build fail pass in 12352
build-amd64-pvops 4 kernel-build fail pass in 12352
test-amd64-i386-xl-credit2 9 guest-start fail in 12352 pass in 12351
test-amd64-i386-qemuu-rhel6hvm-amd 7 redhat-install fail in 12351 pass in 12352
test-amd64-amd64-xl-sedf 9 guest-start fail in 12351 pass in 12352
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-qemuu-rhel6hvm-amd 9 guest-start.2 fail in 12352 like 12278
Tests which did not succeed, but are not blocking:
test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a
test-amd64-i386-rhel6hvm-amd 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-pcipt-intel 1 xen-build-check(1) blocked n/a
test-i386-i386-pv 1 xen-build-check(1) blocked n/a
test-amd64-amd64-pv 1 xen-build-check(1) blocked n/a
test-i386-i386-xl 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-pv 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-multivcpu 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-sedf-pin 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-credit2 1 xen-build-check(1) blocked n/a
test-amd64-amd64-pair 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl 1 xen-build-check(1) blocked n/a
test-amd64-i386-xend-winxpsp3 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-win7-amd64 1 xen-build-check(1) blocked n/a
test-amd64-amd64-win 1 xen-build-check(1) blocked n/a
test-amd64-i386-qemuu-rhel6hvm-amd 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-win7-amd64 1 xen-build-check(1) blocked n/a
test-amd64-i386-win-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-win-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-sedf 1 xen-build-check(1) blocked n/a
test-i386-i386-xl-winxpsp3 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-winxpsp3 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-winxpsp3-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-i386-win 1 xen-build-check(1) blocked n/a
test-amd64-i386-pair 1 xen-build-check(1) blocked n/a
test-i386-i386-pair 1 xen-build-check(1) blocked n/a
test-i386-i386-xl-qemuu-winxpsp3 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-winxpsp3 1 xen-build-check(1) blocked n/a
test-i386-i386-win 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-win7-amd64 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-win 1 xen-build-check(1) blocked n/a
test-i386-i386-xl-win 1 xen-build-check(1) blocked n/a
test-amd64-i386-rhel6hvm-intel 11 leak-check/check fail in 12352 never pass
test-amd64-i386-rhel6hvm-amd 11 leak-check/check fail in 12352 never pass
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail in 12352 never pass
test-amd64-i386-qemuu-rhel6hvm-intel 9 guest-start.2 fail in 12352 never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail in 12352 never pass
test-amd64-i386-xl-win7-amd64 13 guest-stop fail in 12352 never pass
test-amd64-amd64-win 16 leak-check/check fail in 12352 never pass
test-amd64-amd64-xl-win7-amd64 13 guest-stop fail in 12352 never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail in 12352 never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail in 12352 never pass
test-i386-i386-xl-winxpsp3 13 guest-stop fail in 12352 never pass
test-amd64-amd64-xl-winxpsp3 13 guest-stop fail in 12352 never pass
test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail in 12352 never pass
test-amd64-i386-win 16 leak-check/check fail in 12352 never pass
test-i386-i386-xl-qemuu-winxpsp3 7 windows-install fail in 12352 never pass
test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail in 12352 never pass
test-i386-i386-win 16 leak-check/check fail in 12352 never pass
test-amd64-amd64-xl-qemuu-win7-amd64 7 windows-install fail in 12352 never pass
test-amd64-amd64-xl-win 13 guest-stop fail in 12352 never pass
test-i386-i386-xl-win 13 guest-stop fail in 12352 never pass
version targeted for testing:
xen 4e1d091d10d8
baseline version:
xen 4e1d091d10d8
jobs:
build-amd64 pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops fail
build-i386-pvops fail
test-amd64-amd64-xl blocked
test-amd64-i386-xl blocked
test-i386-i386-xl blocked
test-amd64-i386-rhel6hvm-amd blocked
test-amd64-i386-qemuu-rhel6hvm-amd blocked
test-amd64-amd64-xl-qemuu-win7-amd64 blocked
test-amd64-amd64-xl-win7-amd64 blocked
test-amd64-i386-xl-win7-amd64 blocked
test-amd64-i386-xl-credit2 blocked
test-amd64-amd64-xl-pcipt-intel blocked
test-amd64-i386-rhel6hvm-intel blocked
test-amd64-i386-qemuu-rhel6hvm-intel blocked
test-amd64-i386-xl-multivcpu blocked
test-amd64-amd64-pair blocked
test-amd64-i386-pair blocked
test-i386-i386-pair blocked
test-amd64-amd64-xl-sedf-pin blocked
test-amd64-amd64-pv blocked
test-amd64-i386-pv blocked
test-i386-i386-pv blocked
test-amd64-amd64-xl-sedf blocked
test-amd64-i386-win-vcpus1 blocked
test-amd64-i386-xl-win-vcpus1 blocked
test-amd64-i386-xl-winxpsp3-vcpus1 blocked
test-amd64-amd64-win blocked
test-amd64-i386-win blocked
test-i386-i386-win blocked
test-amd64-amd64-xl-win blocked
test-i386-i386-xl-win blocked
test-amd64-amd64-xl-qemuu-winxpsp3 blocked
test-i386-i386-xl-qemuu-winxpsp3 blocked
test-amd64-i386-xend-winxpsp3 blocked
test-amd64-amd64-xl-winxpsp3 blocked
test-i386-i386-xl-winxpsp3 blocked
------------------------------------------------------------
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
Published tested tree is already up to date.
On Mon, 2012-03-19 at 02:44 +0000, xen.org wrote:> flight 12353 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/12353/ > > Failures :-/ but no regressions. > > Tests which are failing intermittently (not blocking): > build-i386-pvops 4 kernel-build fail pass in 12352 > build-amd64-pvops 4 kernel-build fail pass in 12352I thought we had changed things such that *-build were always blocking failures? We don''t seem to have pushed anything on this occasion but in general we wouldn''t want to have done so. Ian.> test-amd64-i386-xl-credit2 9 guest-start fail in 12352 pass in 12351 > test-amd64-i386-qemuu-rhel6hvm-amd 7 redhat-install fail in 12351 pass in 12352 > test-amd64-amd64-xl-sedf 9 guest-start fail in 12351 pass in 12352 > > Regressions which are regarded as allowable (not blocking): > test-amd64-i386-qemuu-rhel6hvm-amd 9 guest-start.2 fail in 12352 like 12278 > > Tests which did not succeed, but are not blocking: > test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a > test-amd64-i386-rhel6hvm-amd 1 xen-build-check(1) blocked n/a > test-amd64-amd64-xl-pcipt-intel 1 xen-build-check(1) blocked n/a > test-i386-i386-pv 1 xen-build-check(1) blocked n/a > test-amd64-amd64-pv 1 xen-build-check(1) blocked n/a > test-i386-i386-xl 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-pv 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl-multivcpu 1 xen-build-check(1) blocked n/a > test-amd64-amd64-xl-sedf-pin 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl-credit2 1 xen-build-check(1) blocked n/a > test-amd64-amd64-pair 1 xen-build-check(1) blocked n/a > test-amd64-amd64-xl 1 xen-build-check(1) blocked n/a > test-amd64-i386-xend-winxpsp3 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl-win7-amd64 1 xen-build-check(1) blocked n/a > test-amd64-amd64-win 1 xen-build-check(1) blocked n/a > test-amd64-i386-qemuu-rhel6hvm-amd 1 xen-build-check(1) blocked n/a > test-amd64-amd64-xl-win7-amd64 1 xen-build-check(1) blocked n/a > test-amd64-i386-win-vcpus1 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl-win-vcpus1 1 xen-build-check(1) blocked n/a > test-amd64-amd64-xl-sedf 1 xen-build-check(1) blocked n/a > test-i386-i386-xl-winxpsp3 1 xen-build-check(1) blocked n/a > test-amd64-amd64-xl-winxpsp3 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl-winxpsp3-vcpus1 1 xen-build-check(1) blocked n/a > test-amd64-i386-win 1 xen-build-check(1) blocked n/a > test-amd64-i386-pair 1 xen-build-check(1) blocked n/a > test-i386-i386-pair 1 xen-build-check(1) blocked n/a > test-i386-i386-xl-qemuu-winxpsp3 1 xen-build-check(1) blocked n/a > test-amd64-amd64-xl-qemuu-winxpsp3 1 xen-build-check(1) blocked n/a > test-i386-i386-win 1 xen-build-check(1) blocked n/a > test-amd64-amd64-xl-qemuu-win7-amd64 1 xen-build-check(1) blocked n/a > test-amd64-amd64-xl-win 1 xen-build-check(1) blocked n/a > test-i386-i386-xl-win 1 xen-build-check(1) blocked n/a > test-amd64-i386-rhel6hvm-intel 11 leak-check/check fail in 12352 never pass > test-amd64-i386-rhel6hvm-amd 11 leak-check/check fail in 12352 never pass > test-amd64-amd64-xl-pcipt-intel 9 guest-start fail in 12352 never pass > test-amd64-i386-qemuu-rhel6hvm-intel 9 guest-start.2 fail in 12352 never pass > test-amd64-i386-xend-winxpsp3 16 leak-check/check fail in 12352 never pass > test-amd64-i386-xl-win7-amd64 13 guest-stop fail in 12352 never pass > test-amd64-amd64-win 16 leak-check/check fail in 12352 never pass > test-amd64-amd64-xl-win7-amd64 13 guest-stop fail in 12352 never pass > test-amd64-i386-win-vcpus1 16 leak-check/check fail in 12352 never pass > test-amd64-i386-xl-win-vcpus1 13 guest-stop fail in 12352 never pass > test-i386-i386-xl-winxpsp3 13 guest-stop fail in 12352 never pass > test-amd64-amd64-xl-winxpsp3 13 guest-stop fail in 12352 never pass > test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail in 12352 never pass > test-amd64-i386-win 16 leak-check/check fail in 12352 never pass > test-i386-i386-xl-qemuu-winxpsp3 7 windows-install fail in 12352 never pass > test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail in 12352 never pass > test-i386-i386-win 16 leak-check/check fail in 12352 never pass > test-amd64-amd64-xl-qemuu-win7-amd64 7 windows-install fail in 12352 never pass > test-amd64-amd64-xl-win 13 guest-stop fail in 12352 never pass > test-i386-i386-xl-win 13 guest-stop fail in 12352 never pass > > version targeted for testing: > xen 4e1d091d10d8 > baseline version: > xen 4e1d091d10d8 > > jobs: > build-amd64 pass > build-i386 pass > build-amd64-oldkern pass > build-i386-oldkern pass > build-amd64-pvops fail > build-i386-pvops fail > test-amd64-amd64-xl blocked > test-amd64-i386-xl blocked > test-i386-i386-xl blocked > test-amd64-i386-rhel6hvm-amd blocked > test-amd64-i386-qemuu-rhel6hvm-amd blocked > test-amd64-amd64-xl-qemuu-win7-amd64 blocked > test-amd64-amd64-xl-win7-amd64 blocked > test-amd64-i386-xl-win7-amd64 blocked > test-amd64-i386-xl-credit2 blocked > test-amd64-amd64-xl-pcipt-intel blocked > test-amd64-i386-rhel6hvm-intel blocked > test-amd64-i386-qemuu-rhel6hvm-intel blocked > test-amd64-i386-xl-multivcpu blocked > test-amd64-amd64-pair blocked > test-amd64-i386-pair blocked > test-i386-i386-pair blocked > test-amd64-amd64-xl-sedf-pin blocked > test-amd64-amd64-pv blocked > test-amd64-i386-pv blocked > test-i386-i386-pv blocked > test-amd64-amd64-xl-sedf blocked > test-amd64-i386-win-vcpus1 blocked > test-amd64-i386-xl-win-vcpus1 blocked > test-amd64-i386-xl-winxpsp3-vcpus1 blocked > test-amd64-amd64-win blocked > test-amd64-i386-win blocked > test-i386-i386-win blocked > test-amd64-amd64-xl-win blocked > test-i386-i386-xl-win blocked > test-amd64-amd64-xl-qemuu-winxpsp3 blocked > test-i386-i386-xl-qemuu-winxpsp3 blocked > test-amd64-i386-xend-winxpsp3 blocked > test-amd64-amd64-xl-winxpsp3 blocked > test-i386-i386-xl-winxpsp3 blocked > > > ------------------------------------------------------------ > 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 > > > Published tested tree is already up to date. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel
>>> On 19.03.12 at 09:44, Ian Campbell <Ian.Campbell@citrix.com> wrote: > On Mon, 2012-03-19 at 02:44 +0000, xen.org wrote: >> flight 12353 xen-unstable real [real] >> http://www.chiark.greenend.org.uk/~xensrcts/logs/12353/ >> >> Failures :-/ but no regressions. >> >> Tests which are failing intermittently (not blocking): >> build-i386-pvops 4 kernel-build fail pass in 12352 >> build-amd64-pvops 4 kernel-build fail pass in 12352 > > I thought we had changed things such that *-build were always blocking > failures? We don''t seem to have pushed anything on this occasion but in > general we wouldn''t want to have done so.Would it really make sense to block hypervisor/tools pushes when kernel builds fail? There are no shared sources, so the builds should be completely independent. Of course, it tests can''t be run because of the build failure, that is a blocking reason, but then the question is whether everything should be built from scratch in the first place (rather than using pre-existing binaries either from an earlier successful run of the same tests or from the most recent successful run against the corresponding tree). Jan
Ian Campbell writes ("Re: [Xen-devel] [xen-unstable test] 12353: tolerable
FAIL"):> On Mon, 2012-03-19 at 02:44 +0000, xen.org wrote:
> > flight 12353 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/12353/
> >
> > Failures :-/ but no regressions.
> >
> > Tests which are failing intermittently (not blocking):
> > build-i386-pvops 4 kernel-build fail pass in
12352
> > build-amd64-pvops 4 kernel-build fail pass in
12352
>
> I thought we had changed things such that *-build were always blocking
> failures? We don''t seem to have pushed anything on this occasion
but in
> general we wouldn''t want to have done so.
This isn''t "blocking" because it''s not a
"regression" because it
failed in the baseline too because the baseline was identical to the
candidate. But nevertheless the report is wrong and I have pushed a
fix which ought to fix that.
(The test system is down ATM because we have had a database problem
which is being sorted out...)
Thanks,
Ian.
Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 12353: tolerable
FAIL"):> Would it really make sense to block hypervisor/tools pushes when
> kernel builds fail?
In principle not but ...
> There are no shared sources, so the builds should
> be completely independent. Of course, it tests can''t be run
because
> of the build failure, that is a blocking reason,
... in general the system doesn''t regard blocked tests as blockers.
It expects the depended-upon action to be a blocker in itself.
> but then the question
> is whether everything should be built from scratch in the first place
> (rather than using pre-existing binaries either from an earlier
> successful run of the same tests or from the most recent successful
> run against the corresponding tree).
That would be possible and I have some code to do this for bisections
but it''s more complicated here.
In practice these builds fail rarely enough that it''s not a problem.
If they do fail because the upstream sites are down they are failing
for other people too and I would think that the best way to deal with
that is to reduce the number of sites we depend on.
Ian.