flight 16207 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/16207/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-win7-amd64 7 windows-install fail REGR. vs. 16171 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-sedf-pin 5 xen-boot fail like 16171 test-amd64-amd64-xl-sedf 5 xen-boot fail like 16171 test-amd64-amd64-xl-qemut-win 7 windows-install fail like 16171 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass test-amd64-i386-win 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-win-vcpus1 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass test-amd64-i386-qemut-win-vcpus1 16 leak-check/check 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-qemut-win 16 leak-check/check fail never pass test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop fail never pass test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass test-amd64-amd64-qemut-win 16 leak-check/check fail never pass test-amd64-amd64-win 16 leak-check/check fail never pass test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop fail never pass test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass test-amd64-amd64-xl-win 13 guest-stop fail never pass version targeted for testing: xen 620e5d3aa7cd baseline version: xen 788f4551580d ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@citrix.com> Boris Ostrovsky <boris.ostrovsky@oracle.com> Eddie Dong <eddie.dong@intel.com> Fabio Fantoni <fabio.fantoni@heliman.it> Frediano Ziglio <frediano.ziglio@citrix.com> Ian Campbell <ian.campbell@citrix.com> Ian Jackson <ian.jackson@eu.citrix.com> Jan Beulich <jbeulich@suse.com> Jiongxi Li <jiongxi.li@intel.com> Jun Nakajima <jun.nakajima@intel.com> Keir Fraser <keir@xen.org> Lalith Suresh <suresh.lalith@gmail.com> Olaf Hering <olaf@aepfle.de> Ross Philipson <ross.philipson@citrix.com> Shakeel Butt <shakeel.butt@gmail.com> Stefano Stabellini <stefano.stabellini@eu.citrix.com> Tim Deegan <tim@xen.org> ------------------------------------------------------------ jobs: build-amd64 pass build-armhf 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-amd64-i386-rhel6hvm-amd pass test-amd64-i386-qemut-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass 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 pass test-amd64-amd64-xl-pcipt-intel fail test-amd64-i386-rhel6hvm-intel pass test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-i386-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-xl-sedf-pin fail test-amd64-amd64-pv pass test-amd64-i386-pv pass 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. (No revision log; it would be 762 lines long.)
On Tue, 2013-02-19 at 05:42 +0000, xen.org wrote:> flight 16207 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/16207/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-xl-qemut-win7-amd64 7 windows-install fail REGR. vs. 16171This looks distressingly similar to the failure in 15401 which we overrode with a manual push on the basis that 15179 was a fluke pass. Although I suppose one Windows install regression looks much like any other... Ian.
>>> On 19.02.13 at 10:02, Ian Campbell <Ian.Campbell@citrix.com> wrote: > On Tue, 2013-02-19 at 05:42 +0000, xen.org wrote: >> flight 16207 xen-unstable real [real] >> http://www.chiark.greenend.org.uk/~xensrcts/logs/16207/ >> >> Regressions :-( >> >> Tests which did not succeed and are blocking, >> including tests which could not be run: >> test-amd64-amd64-xl-qemut-win7-amd64 7 windows-install fail REGR. vs. > 16171 > > This looks distressingly similar to the failure in 15401 which we > overrode with a manual push on the basis that 15179 was a fluke pass. > Although I suppose one Windows install regression looks much like any > other...On closer inspection I''m not as certain about the similarity: Back then, Windows was not completing a shutdown, i.e. waiting for some event to happen (looking at/playing with the LAPIC) to make progress. Here, Windows sits at the logon screen (and both vCPU-s are idle), yet the VM apparently can''t be reached over the network. But there nevertheless must be some sort of problem (possibly a regression, but could as well be an intermittent problem now being exposed more readily), as earlier that other qemut-win test didn''t consistently fail, and the test above didn''t fail that frequently either. Jan