flight 17105 linux-mingo-tip-master real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/17105/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl 5 xen-boot fail REGR. vs. 12678
test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 12678
test-amd64-amd64-win 5 xen-boot fail REGR. vs. 12678
test-amd64-amd64-xl-qemuu-win7-amd64 5 xen-boot fail REGR. vs. 12678
test-amd64-amd64-xl-qemuu-winxpsp3 5 xen-boot fail REGR. vs. 12678
test-amd64-i386-xl 5 xen-boot fail REGR. vs. 12678
test-amd64-i386-rhel6hvm-intel 5 xen-boot fail REGR. vs. 12678
test-amd64-i386-pv 5 xen-boot fail REGR. vs. 12678
test-amd64-amd64-xl-winxpsp3 5 xen-boot fail REGR. vs. 12678
test-amd64-amd64-pv 5 xen-boot fail REGR. vs. 12678
test-amd64-i386-win 7 windows-install fail REGR. vs. 12678
test-amd64-amd64-pair 8 xen-boot/dst_host fail REGR. vs. 12678
test-amd64-amd64-pair 7 xen-boot/src_host fail REGR. vs. 12678
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-sedf 5 xen-boot fail REGR. vs. 12678
test-amd64-amd64-xl-sedf-pin 5 xen-boot fail REGR. vs. 12678
test-amd64-i386-qemut-rhel6hvm-intel 5 xen-boot fail blocked in 12678
test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail blocked in 12678
test-amd64-i386-rhel6hvm-amd 7 redhat-install fail like 12678
test-amd64-i386-qemuu-rhel6hvm-amd 7 redhat-install fail like 12678
test-amd64-i386-xl-multivcpu 7 debian-install fail like 12678
test-amd64-i386-pair 8 xen-boot/dst_host fail like 12678
test-amd64-i386-pair 7 xen-boot/src_host fail like 12678
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-credit2 15 guest-stop fail never pass
test-amd64-amd64-qemut-win 5 xen-boot fail never pass
test-amd64-amd64-xl-qemut-win7-amd64 5 xen-boot fail never pass
test-amd64-amd64-xl-win7-amd64 5 xen-boot fail never pass
test-amd64-amd64-xl-qemut-winxpsp3 5 xen-boot fail never pass
test-amd64-amd64-xl-qemut-win 5 xen-boot fail never pass
test-amd64-amd64-xl-pcipt-intel 5 xen-boot fail never pass
test-amd64-i386-xl-win-vcpus1 5 xen-boot fail never pass
test-amd64-i386-xl-qemut-win-vcpus1 7 windows-install fail never pass
test-amd64-i386-qemut-win 7 windows-install fail never pass
test-amd64-i386-xl-qemut-win7-amd64 7 windows-install fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail never pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-qemut-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
version targeted for testing:
linux f37ae0b3f120403ba2d324159fdb1a953ed19e20
baseline version:
linux d935d0f77650fea53986811ca8a2f8c726fd9857
jobs:
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl fail
test-amd64-i386-xl fail
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-qemut-rhel6hvm-amd fail
test-amd64-i386-qemuu-rhel6hvm-amd fail
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 fail
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-qemut-rhel6hvm-intel fail
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-i386-xl-multivcpu fail
test-amd64-amd64-pair fail
test-amd64-i386-pair fail
test-amd64-amd64-xl-sedf-pin fail
test-amd64-amd64-pv fail
test-amd64-i386-pv fail
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-amd64-amd64-qemut-win fail
test-amd64-i386-qemut-win fail
test-amd64-amd64-xl-qemut-win fail
test-amd64-amd64-xl-win fail
test-amd64-i386-xend-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-amd64-i386-xend-winxpsp3 fail
test-amd64-amd64-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.
Konrad Rzeszutek Wilk
2013-Mar-05 16:13 UTC
Re: [linux-mingo-tip-master test] 17105: regressions - FAIL
On Tue, Mar 05, 2013 at 12:51:11PM +0000, xen.org wrote:> flight 17105 linux-mingo-tip-master real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/17105/ > > Regressions :-(Ian, I poked hpa about it and he mentioned that Ingo sporadically updates his tree. So going to poke him in a week since v3.9-rc1 just came out.> > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-xl 5 xen-boot fail REGR. vs. 12678 > test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 12678 > test-amd64-amd64-win 5 xen-boot fail REGR. vs. 12678 > test-amd64-amd64-xl-qemuu-win7-amd64 5 xen-boot fail REGR. vs. 12678 > test-amd64-amd64-xl-qemuu-winxpsp3 5 xen-boot fail REGR. vs. 12678 > test-amd64-i386-xl 5 xen-boot fail REGR. vs. 12678 > test-amd64-i386-rhel6hvm-intel 5 xen-boot fail REGR. vs. 12678 > test-amd64-i386-pv 5 xen-boot fail REGR. vs. 12678 > test-amd64-amd64-xl-winxpsp3 5 xen-boot fail REGR. vs. 12678 > test-amd64-amd64-pv 5 xen-boot fail REGR. vs. 12678 > test-amd64-i386-win 7 windows-install fail REGR. vs. 12678 > test-amd64-amd64-pair 8 xen-boot/dst_host fail REGR. vs. 12678 > test-amd64-amd64-pair 7 xen-boot/src_host fail REGR. vs. 12678 > > Regressions which are regarded as allowable (not blocking): > test-amd64-amd64-xl-sedf 5 xen-boot fail REGR. vs. 12678 > test-amd64-amd64-xl-sedf-pin 5 xen-boot fail REGR. vs. 12678 > test-amd64-i386-qemut-rhel6hvm-intel 5 xen-boot fail blocked in 12678 > test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail blocked in 12678 > test-amd64-i386-rhel6hvm-amd 7 redhat-install fail like 12678 > test-amd64-i386-qemuu-rhel6hvm-amd 7 redhat-install fail like 12678 > test-amd64-i386-xl-multivcpu 7 debian-install fail like 12678 > test-amd64-i386-pair 8 xen-boot/dst_host fail like 12678 > test-amd64-i386-pair 7 xen-boot/src_host fail like 12678 > > Tests which did not succeed, but are not blocking: > test-amd64-i386-xl-credit2 15 guest-stop fail never pass > test-amd64-amd64-qemut-win 5 xen-boot fail never pass > test-amd64-amd64-xl-qemut-win7-amd64 5 xen-boot fail never pass > test-amd64-amd64-xl-win7-amd64 5 xen-boot fail never pass > test-amd64-amd64-xl-qemut-winxpsp3 5 xen-boot fail never pass > test-amd64-amd64-xl-qemut-win 5 xen-boot fail never pass > test-amd64-amd64-xl-pcipt-intel 5 xen-boot fail never pass > test-amd64-i386-xl-win-vcpus1 5 xen-boot fail never pass > test-amd64-i386-xl-qemut-win-vcpus1 7 windows-install fail never pass > test-amd64-i386-qemut-win 7 windows-install fail never pass > test-amd64-i386-xl-qemut-win7-amd64 7 windows-install fail never pass > test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass > test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail never pass > test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass > test-amd64-i386-qemut-win-vcpus1 16 leak-check/check fail never pass > test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass > test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass > test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass > > version targeted for testing: > linux f37ae0b3f120403ba2d324159fdb1a953ed19e20 > baseline version: > linux d935d0f77650fea53986811ca8a2f8c726fd9857 > > jobs: > build-amd64 pass > build-armhf pass > build-i386 pass > build-amd64-pvops pass > build-i386-pvops pass > test-amd64-amd64-xl fail > test-amd64-i386-xl fail > test-amd64-i386-rhel6hvm-amd fail > test-amd64-i386-qemut-rhel6hvm-amd fail > test-amd64-i386-qemuu-rhel6hvm-amd fail > 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 fail > test-amd64-amd64-xl-pcipt-intel fail > test-amd64-i386-rhel6hvm-intel fail > test-amd64-i386-qemut-rhel6hvm-intel fail > test-amd64-i386-qemuu-rhel6hvm-intel pass > test-amd64-i386-xl-multivcpu fail > test-amd64-amd64-pair fail > test-amd64-i386-pair fail > test-amd64-amd64-xl-sedf-pin fail > test-amd64-amd64-pv fail > test-amd64-i386-pv fail > 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-amd64-amd64-qemut-win fail > test-amd64-i386-qemut-win fail > test-amd64-amd64-xl-qemut-win fail > test-amd64-amd64-xl-win fail > test-amd64-i386-xend-qemut-winxpsp3 fail > test-amd64-amd64-xl-qemut-winxpsp3 fail > test-amd64-amd64-xl-qemuu-winxpsp3 fail > test-amd64-i386-xend-winxpsp3 fail > test-amd64-amd64-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 >
Sander Eikelenboom
2013-Mar-05 16:26 UTC
Re: [linux-mingo-tip-master test] 17105: regressions - FAIL
Tuesday, March 5, 2013, 5:13:10 PM, you wrote:> On Tue, Mar 05, 2013 at 12:51:11PM +0000, xen.org wrote: >> flight 17105 linux-mingo-tip-master real [real] >> http://www.chiark.greenend.org.uk/~xensrcts/logs/17105/ >> >> Regressions :-(> Ian,> I poked hpa about it and he mentioned that Ingo sporadically updates > his tree. So going to poke him in a week since v3.9-rc1 just > came out.Would it be an idea to setup a branch (in konrad''s tree) that follows tip-master, but allows konrad to apply patches that are "under way" (accepted but not yet applied) and are important (needed to boot etc ?) and test that one instead ?>> >> Tests which did not succeed and are blocking, >> including tests which could not be run: >> test-amd64-amd64-xl 5 xen-boot fail REGR. vs. 12678 >> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 12678 >> test-amd64-amd64-win 5 xen-boot fail REGR. vs. 12678 >> test-amd64-amd64-xl-qemuu-win7-amd64 5 xen-boot fail REGR. vs. 12678 >> test-amd64-amd64-xl-qemuu-winxpsp3 5 xen-boot fail REGR. vs. 12678 >> test-amd64-i386-xl 5 xen-boot fail REGR. vs. 12678 >> test-amd64-i386-rhel6hvm-intel 5 xen-boot fail REGR. vs. 12678 >> test-amd64-i386-pv 5 xen-boot fail REGR. vs. 12678 >> test-amd64-amd64-xl-winxpsp3 5 xen-boot fail REGR. vs. 12678 >> test-amd64-amd64-pv 5 xen-boot fail REGR. vs. 12678 >> test-amd64-i386-win 7 windows-install fail REGR. vs. 12678 >> test-amd64-amd64-pair 8 xen-boot/dst_host fail REGR. vs. 12678 >> test-amd64-amd64-pair 7 xen-boot/src_host fail REGR. vs. 12678 >> >> Regressions which are regarded as allowable (not blocking): >> test-amd64-amd64-xl-sedf 5 xen-boot fail REGR. vs. 12678 >> test-amd64-amd64-xl-sedf-pin 5 xen-boot fail REGR. vs. 12678 >> test-amd64-i386-qemut-rhel6hvm-intel 5 xen-boot fail blocked in 12678 >> test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail blocked in 12678 >> test-amd64-i386-rhel6hvm-amd 7 redhat-install fail like 12678 >> test-amd64-i386-qemuu-rhel6hvm-amd 7 redhat-install fail like 12678 >> test-amd64-i386-xl-multivcpu 7 debian-install fail like 12678 >> test-amd64-i386-pair 8 xen-boot/dst_host fail like 12678 >> test-amd64-i386-pair 7 xen-boot/src_host fail like 12678 >> >> Tests which did not succeed, but are not blocking: >> test-amd64-i386-xl-credit2 15 guest-stop fail never pass >> test-amd64-amd64-qemut-win 5 xen-boot fail never pass >> test-amd64-amd64-xl-qemut-win7-amd64 5 xen-boot fail never pass >> test-amd64-amd64-xl-win7-amd64 5 xen-boot fail never pass >> test-amd64-amd64-xl-qemut-winxpsp3 5 xen-boot fail never pass >> test-amd64-amd64-xl-qemut-win 5 xen-boot fail never pass >> test-amd64-amd64-xl-pcipt-intel 5 xen-boot fail never pass >> test-amd64-i386-xl-win-vcpus1 5 xen-boot fail never pass >> test-amd64-i386-xl-qemut-win-vcpus1 7 windows-install fail never pass >> test-amd64-i386-qemut-win 7 windows-install fail never pass >> test-amd64-i386-xl-qemut-win7-amd64 7 windows-install fail never pass >> test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass >> test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail never pass >> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass >> test-amd64-i386-qemut-win-vcpus1 16 leak-check/check fail never pass >> test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass >> test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass >> test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass >> >> version targeted for testing: >> linux f37ae0b3f120403ba2d324159fdb1a953ed19e20 >> baseline version: >> linux d935d0f77650fea53986811ca8a2f8c726fd9857 >> >> jobs: >> build-amd64 pass >> build-armhf pass >> build-i386 pass >> build-amd64-pvops pass >> build-i386-pvops pass >> test-amd64-amd64-xl fail >> test-amd64-i386-xl fail >> test-amd64-i386-rhel6hvm-amd fail >> test-amd64-i386-qemut-rhel6hvm-amd fail >> test-amd64-i386-qemuu-rhel6hvm-amd fail >> 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 fail >> test-amd64-amd64-xl-pcipt-intel fail >> test-amd64-i386-rhel6hvm-intel fail >> test-amd64-i386-qemut-rhel6hvm-intel fail >> test-amd64-i386-qemuu-rhel6hvm-intel pass >> test-amd64-i386-xl-multivcpu fail >> test-amd64-amd64-pair fail >> test-amd64-i386-pair fail >> test-amd64-amd64-xl-sedf-pin fail >> test-amd64-amd64-pv fail >> test-amd64-i386-pv fail >> 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-amd64-amd64-qemut-win fail >> test-amd64-i386-qemut-win fail >> test-amd64-amd64-xl-qemut-win fail >> test-amd64-amd64-xl-win fail >> test-amd64-i386-xend-qemut-winxpsp3 fail >> test-amd64-amd64-xl-qemut-winxpsp3 fail >> test-amd64-amd64-xl-qemuu-winxpsp3 fail >> test-amd64-i386-xend-winxpsp3 fail >> test-amd64-amd64-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 >>
Ian Jackson
2013-Mar-05 16:29 UTC
Re: [linux-mingo-tip-master test] 17105: regressions - FAIL
Sander Eikelenboom writes ("Re: [Xen-devel] [linux-mingo-tip-master test]
17105: regressions - FAIL"):> Tuesday, March 5, 2013, 5:13:10 PM, you wrote:
> > I poked hpa about it and he mentioned that Ingo sporadically updates
> > his tree. So going to poke him in a week since v3.9-rc1 just
> > came out.
>
> Would it be an idea to setup a branch (in konrad''s tree) that
follows tip-master, but allows konrad to apply patches that are "under
way" (accepted but not yet applied) and are important (needed to boot etc
?) and test that one instead ?
That would be simple from my pov. I don''t have an opinion about it.
Ian.
Sander Eikelenboom
2013-Mar-05 16:37 UTC
Re: [linux-mingo-tip-master test] 17105: regressions - FAIL
Tuesday, March 5, 2013, 5:29:22 PM, you wrote:> Sander Eikelenboom writes ("Re: [Xen-devel] [linux-mingo-tip-master test] 17105: regressions - FAIL"): >> Tuesday, March 5, 2013, 5:13:10 PM, you wrote: >> > I poked hpa about it and he mentioned that Ingo sporadically updates >> > his tree. So going to poke him in a week since v3.9-rc1 just >> > came out. >> >> Would it be an idea to setup a branch (in konrad''s tree) that follows tip-master, but allows konrad to apply patches that are "under way" (accepted but not yet applied) and are important (needed to boot etc ?) and test that one instead ?> That would be simple from my pov. I don''t have an opinion about it.It''s as always a tradeoff, an extra burden for Konrad, but less wastage of test resources. Could be something like a "linux-next" but then only for Xen-patches applied on top of branch tracking perhaps the most important tree (x86). Testing linux-next it self could probably hang on to many non Xen related problems.> Ian.
Konrad Rzeszutek Wilk
2013-Mar-05 18:16 UTC
Re: [linux-mingo-tip-master test] 17105: regressions - FAIL
On Tue, Mar 05, 2013 at 05:37:50PM +0100, Sander Eikelenboom wrote:> > Tuesday, March 5, 2013, 5:29:22 PM, you wrote: > > > Sander Eikelenboom writes ("Re: [Xen-devel] [linux-mingo-tip-master test] 17105: regressions - FAIL"): > >> Tuesday, March 5, 2013, 5:13:10 PM, you wrote: > >> > I poked hpa about it and he mentioned that Ingo sporadically updates > >> > his tree. So going to poke him in a week since v3.9-rc1 just > >> > came out. > >> > >> Would it be an idea to setup a branch (in konrad''s tree) that follows tip-master, but allows konrad to apply patches that are "under way" (accepted but not yet applied) and are important (needed to boot etc ?) and test that one instead ? > > > That would be simple from my pov. I don''t have an opinion about it. > > It''s as always a tradeoff, an extra burden for Konrad, but less wastage of test resources. > Could be something like a "linux-next" but then only for Xen-patches applied on top of branch tracking perhaps the most important tree (x86). > Testing linux-next it self could probably hang on to many non Xen related problems.Actually, linux-next could be a good option too. It is suppose to be the next thing going to Linus so hopefully working. Ian, would it be possible to set this up?> > > Ian. > >