xen.org
2013-Mar-07 05:10 UTC
[qemu-upstream-4.2-testing test] 17115: regressions - trouble: broken/fail/pass
flight 17115 qemu-upstream-4.2-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/17115/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-i386-i386-xl-qemuu-winxpsp3 7 windows-install fail in 17084 REGR. vs.
15122
Tests which are failing intermittently (not blocking):
test-i386-i386-xl-qemuu-winxpsp3 3 host-install(3) broken pass in 17084
Tests which did not succeed, but are not blocking:
build-armhf 4 xen-build fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-win 13 guest-stop fail never pass
test-amd64-i386-qemuu-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-qemuu-win 16 leak-check/check fail never pass
test-i386-i386-qemuu-win 16 leak-check/check fail never pass
test-amd64-i386-xl-qemuu-win-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xend-qemuu-winxpsp3 16 leak-check/check fail never pass
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 13 guest-stop fail never pass
test-i386-i386-xl-qemuu-win 12 guest-localmigrate/x10 fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-qemuu-win 16 leak-check/check fail never pass
test-amd64-i386-xl-qemuu-win7-amd64 13 guest-stop fail never pass
version targeted for testing:
qemuu eccc68722696864fc4823f048c7be58d11281b97
baseline version:
qemuu 70454385eeee6f0b3f7a9eddca9f7340b5060824
------------------------------------------------------------
People who touched revisions under test:
Alex Bligh <alex@alex.org.uk>
Anthony PERARD <anthony.perard@citrix.com>
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf fail
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-i386-qemuu-win-vcpus1 fail
test-amd64-i386-xl-qemuu-win-vcpus1 fail
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail
test-amd64-amd64-qemuu-win fail
test-amd64-i386-qemuu-win fail
test-i386-i386-qemuu-win fail
test-amd64-amd64-xl-qemuu-win fail
test-i386-i386-xl-qemuu-win fail
test-amd64-i386-xend-qemuu-winxpsp3 fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-i386-i386-xl-qemuu-winxpsp3 broken
------------------------------------------------------------
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 eccc68722696864fc4823f048c7be58d11281b97
Author: Anthony PERARD <anthony.perard@citrix.com>
Date: Thu Feb 21 12:16:42 2013 +0000
xen: Set the vram dirty when an error occurs.
If the call to xc_hvm_track_dirty_vram() fails, then we set dirtybit on all
the
video ram. This case happens during migration.
Backport of 8aba7dc02d5660df7e7d8651304b3079908358be
This backport is less clean that it might be because there is no
memory_region_set_dirty that copes with more than one page in 4.2,
and the case where the call to xc_hvm_track_dirty_vram is
successful also needs to ensure xen_modified_memory is
called (which would on unstable have been done within
memory_region_set_dirty).
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Signed-off-by: Alex Bligh <alex@alex.org.uk>
Alex Bligh
2013-Mar-07 09:45 UTC
Re: [qemu-upstream-4.2-testing test] 17115: regressions - trouble: broken/fail/pass
I think this is because the qemu tag has not been changed. Alex --On 7 March 2013 05:10:48 +0000 "xen.org" <ian.jackson@eu.citrix.com> wrote:> flight 17115 qemu-upstream-4.2-testing real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/17115/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-i386-i386-xl-qemuu-winxpsp3 7 windows-install fail in 17084 REGR. vs. 15122 > > Tests which are failing intermittently (not blocking): > test-i386-i386-xl-qemuu-winxpsp3 3 host-install(3) broken pass in 17084 > > Tests which did not succeed, but are not blocking: > build-armhf 4 xen-build fail never pass > test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass > test-amd64-amd64-xl-qemuu-win 13 guest-stop fail never pass > test-amd64-i386-qemuu-win-vcpus1 16 leak-check/check fail never pass > test-amd64-i386-qemuu-win 16 leak-check/check fail never pass > test-i386-i386-qemuu-win 16 leak-check/check fail never pass > test-amd64-i386-xl-qemuu-win-vcpus1 13 guest-stop fail never pass > test-amd64-i386-xend-qemuu-winxpsp3 16 leak-check/check fail never pass > test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 13 guest-stop fail never pass > test-i386-i386-xl-qemuu-win 12 guest-localmigrate/x10 fail never pass > test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass > test-amd64-amd64-qemuu-win 16 leak-check/check fail never pass > test-amd64-i386-xl-qemuu-win7-amd64 13 guest-stop fail never pass > > version targeted for testing: > qemuu eccc68722696864fc4823f048c7be58d11281b97 > baseline version: > qemuu 70454385eeee6f0b3f7a9eddca9f7340b5060824 > > ------------------------------------------------------------ > People who touched revisions under test: > Alex Bligh <alex@alex.org.uk> > Anthony PERARD <anthony.perard@citrix.com> > Stefano Stabellini <stefano.stabellini@eu.citrix.com> > ------------------------------------------------------------ > > jobs: > build-amd64 pass > build-armhf fail > build-i386 pass > build-amd64-oldkern pass > build-i386-oldkern pass > build-amd64-pvops pass > build-i386-pvops pass > test-amd64-i386-qemuu-rhel6hvm-amd pass > test-amd64-amd64-xl-qemuu-win7-amd64 fail > test-amd64-i386-xl-qemuu-win7-amd64 fail > test-amd64-i386-qemuu-rhel6hvm-intel pass > test-amd64-i386-qemuu-win-vcpus1 fail > test-amd64-i386-xl-qemuu-win-vcpus1 fail > test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail > test-amd64-amd64-qemuu-win fail > test-amd64-i386-qemuu-win fail > test-i386-i386-qemuu-win fail > test-amd64-amd64-xl-qemuu-win fail > test-i386-i386-xl-qemuu-win fail > test-amd64-i386-xend-qemuu-winxpsp3 fail > test-amd64-amd64-xl-qemuu-winxpsp3 fail > test-i386-i386-xl-qemuu-winxpsp3 broken > > > ------------------------------------------------------------ > 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 eccc68722696864fc4823f048c7be58d11281b97 > Author: Anthony PERARD <anthony.perard@citrix.com> > Date: Thu Feb 21 12:16:42 2013 +0000 > > xen: Set the vram dirty when an error occurs. > > If the call to xc_hvm_track_dirty_vram() fails, then we set dirtybit on all the > video ram. This case happens during migration. > > Backport of 8aba7dc02d5660df7e7d8651304b3079908358be > > This backport is less clean that it might be because there is no > memory_region_set_dirty that copes with more than one page in 4.2, > and the case where the call to xc_hvm_track_dirty_vram is > successful also needs to ensure xen_modified_memory is > called (which would on unstable have been done within > memory_region_set_dirty). > > Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> > Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> > Signed-off-by: Alex Bligh <alex@alex.org.uk> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > >-- Alex Bligh
Jan Beulich
2013-Mar-07 10:43 UTC
Re: [qemu-upstream-4.2-testing test] 17115: regressions - trouble: broken/fail/pass
>>> On 07.03.13 at 10:45, Alex Bligh <alex@alex.org.uk> wrote: > I think this is because the qemu tag has not been changed.I think this run simple didn''t pick up the change. The not updated tag - afaiui - would only affect xen-4.2-testing tests. And I think we really should only do one more update to the tag (in the context here): Either revert back to the previous value, or set to the one resulting from the most change. To know which one first requires a qemu-upstream-4.2-testing test to complete with that most recent change included. Jan> --On 7 March 2013 05:10:48 +0000 "xen.org" <ian.jackson@eu.citrix.com> wrote: > >> flight 17115 qemu-upstream-4.2-testing real [real] >> http://www.chiark.greenend.org.uk/~xensrcts/logs/17115/ >> >> Regressions :-( >> >> Tests which did not succeed and are blocking, >> including tests which could not be run: >> test-i386-i386-xl-qemuu-winxpsp3 7 windows-install fail in 17084 REGR. vs. 15122 >> >> Tests which are failing intermittently (not blocking): >> test-i386-i386-xl-qemuu-winxpsp3 3 host-install(3) broken pass in 17084 >> >> Tests which did not succeed, but are not blocking: >> build-armhf 4 xen-build fail never > pass >> test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass >> test-amd64-amd64-xl-qemuu-win 13 guest-stop fail never pass >> test-amd64-i386-qemuu-win-vcpus1 16 leak-check/check fail never pass >> test-amd64-i386-qemuu-win 16 leak-check/check fail never pass >> test-i386-i386-qemuu-win 16 leak-check/check fail never pass >> test-amd64-i386-xl-qemuu-win-vcpus1 13 guest-stop fail never pass >> test-amd64-i386-xend-qemuu-winxpsp3 16 leak-check/check fail never pass >> test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 13 guest-stop fail never pass >> test-i386-i386-xl-qemuu-win 12 guest-localmigrate/x10 fail never pass >> test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass >> test-amd64-amd64-qemuu-win 16 leak-check/check fail never pass >> test-amd64-i386-xl-qemuu-win7-amd64 13 guest-stop fail never pass >> >> version targeted for testing: >> qemuu eccc68722696864fc4823f048c7be58d11281b97 >> baseline version: >> qemuu 70454385eeee6f0b3f7a9eddca9f7340b5060824 >> >> ------------------------------------------------------------ >> People who touched revisions under test: >> Alex Bligh <alex@alex.org.uk> >> Anthony PERARD <anthony.perard@citrix.com> >> Stefano Stabellini <stefano.stabellini@eu.citrix.com> >> ------------------------------------------------------------ >> >> jobs: >> build-amd64 pass >> build-armhf fail >> build-i386 pass >> build-amd64-oldkern pass >> build-i386-oldkern pass >> build-amd64-pvops pass >> build-i386-pvops pass >> test-amd64-i386-qemuu-rhel6hvm-amd pass >> test-amd64-amd64-xl-qemuu-win7-amd64 fail >> test-amd64-i386-xl-qemuu-win7-amd64 fail >> test-amd64-i386-qemuu-rhel6hvm-intel pass >> test-amd64-i386-qemuu-win-vcpus1 fail >> test-amd64-i386-xl-qemuu-win-vcpus1 fail >> test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail >> test-amd64-amd64-qemuu-win fail >> test-amd64-i386-qemuu-win fail >> test-i386-i386-qemuu-win fail >> test-amd64-amd64-xl-qemuu-win fail >> test-i386-i386-xl-qemuu-win fail >> test-amd64-i386-xend-qemuu-winxpsp3 fail >> test-amd64-amd64-xl-qemuu-winxpsp3 fail >> test-i386-i386-xl-qemuu-winxpsp3 broken >> >> >> ------------------------------------------------------------ >> 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 eccc68722696864fc4823f048c7be58d11281b97 >> Author: Anthony PERARD <anthony.perard@citrix.com> >> Date: Thu Feb 21 12:16:42 2013 +0000 >> >> xen: Set the vram dirty when an error occurs. >> >> If the call to xc_hvm_track_dirty_vram() fails, then we set dirtybit on > all the >> video ram. This case happens during migration. >> >> Backport of 8aba7dc02d5660df7e7d8651304b3079908358be >> >> This backport is less clean that it might be because there is no >> memory_region_set_dirty that copes with more than one page in 4.2, >> and the case where the call to xc_hvm_track_dirty_vram is >> successful also needs to ensure xen_modified_memory is >> called (which would on unstable have been done within >> memory_region_set_dirty). >> >> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> >> Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> >> Signed-off-by: Alex Bligh <alex@alex.org.uk> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xen.org >> http://lists.xen.org/xen-devel >> >> > > > > -- > Alex Bligh > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel
Alex Bligh
2013-Mar-07 10:55 UTC
Re: [qemu-upstream-4.2-testing test] 17115: regressions - trouble: broken/fail/pass
Jan, --On 7 March 2013 10:43:06 +0000 Jan Beulich <JBeulich@suse.com> wrote:>>>> On 07.03.13 at 10:45, Alex Bligh <alex@alex.org.uk> wrote: >> I think this is because the qemu tag has not been changed. > > I think this run simple didn''t pick up the change. The not updated > tag - afaiui - would only affect xen-4.2-testing tests. And I think we > really should only do one more update to the tag (in the context > here): Either revert back to the previous value, or set to the one > resulting from the most change. To know which one first requires a > qemu-upstream-4.2-testing test to complete with that most recent > change included.I think I understand. To be honest I''m finding the automatic testing combined with the qemu and xen split, combined with the git changes a little confusing ... -- Alex Bligh
Jan Beulich
2013-Mar-07 11:20 UTC
Re: [qemu-upstream-4.2-testing test] 17115: regressions - trouble: broken/fail/pass
>>> On 07.03.13 at 11:55, Alex Bligh <alex@alex.org.uk> wrote: > --On 7 March 2013 10:43:06 +0000 Jan Beulich <JBeulich@suse.com> wrote: >>>>> On 07.03.13 at 10:45, Alex Bligh <alex@alex.org.uk> wrote: >>> I think this is because the qemu tag has not been changed. >> >> I think this run simple didn''t pick up the change. The not updated >> tag - afaiui - would only affect xen-4.2-testing tests. And I think we >> really should only do one more update to the tag (in the context >> here): Either revert back to the previous value, or set to the one >> resulting from the most change. To know which one first requires a >> qemu-upstream-4.2-testing test to complete with that most recent >> change included. > > I think I understand. To be honest I''m finding the automatic testing > combined with the qemu and xen split, combined with the git changes > a little confusing ...But the way it''s done it makes certain that the tests of the separate trees use a sane state of the other tree(s), rather than exposing regressions that aren''t caused by changes to the tree under test. Jan
Ian Jackson
2013-Mar-07 11:58 UTC
Re: [qemu-upstream-4.2-testing test] 17115: regressions - trouble: broken/fail/pass
Alex Bligh writes ("Re: [Xen-devel] [qemu-upstream-4.2-testing test] 17115:
regressions - trouble: broken/fail/pass"):> I think this is because the qemu tag has not been changed.
No, it''s because this test run started before that change was pushed.
The tests in the push gate for qemu-upstream-4.2-testing don''t look at
the qemu tag in the xen tree.
Ian.
Ian Jackson
2013-Mar-08 15:28 UTC
Re: [qemu-upstream-4.2-testing test] 17115: regressions - trouble: broken/fail/pass [and 1 more messages]
xen.org writes ("[qemu-upstream-4.2-testing test] 17143: tolerable FAIL -
PUSHED"):> flight 17143 qemu-upstream-4.2-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/17143/
>
> Failures :-/ but no regressions.
> version targeted for testing:
> qemuu 351f94ff4bf3a7795ca5b282305aa610e598eec0
> baseline version:
> qemuu 70454385eeee6f0b3f7a9eddca9f7340b5060824
I have updated the QEMU_UPSTREAM_REVISION in staging-4.2.
Ian.