|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.7-testing test] 101668: regressions - FAIL
flight 101668 xen-4.7-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/101668/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pair 20 guest-start/debian fail REGR. vs. 101272 test-amd64-i386-qemuu-rhel6hvm-intel 10 guest-stop fail REGR. vs. 101272 test-armhf-armhf-libvirt 13 saverestore-support-check fail REGR. vs. 101272 test-armhf-armhf-libvirt-xsm 13 saverestore-support-check fail REGR. vs. 101272 test-armhf-armhf-libvirt-qcow2 12 saverestore-support-check fail REGR. vs. 101272 test-armhf-armhf-libvirt-raw 12 saverestore-support-check fail REGR. vs. 101272 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds 15 guest-start/debian.repeat fail REGR. vs. 101272 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 101272 test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 101272 test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 101272 Tests which did not succeed, but are not blocking: test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-xl 12 migrate-support-check fail never pass test-armhf-armhf-xl 13 saverestore-support-check fail never pass test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt 15 guest-start/debian.repeat fail never pass test-armhf-armhf-xl-xsm 12 migrate-support-check fail never pass test-armhf-armhf-xl-xsm 13 saverestore-support-check fail never pass test-armhf-armhf-xl-arndale 12 migrate-support-check fail never pass test-armhf-armhf-xl-arndale 13 saverestore-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 12 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 13 saverestore-support-check fail never pass test-armhf-armhf-xl-cubietruck 12 migrate-support-check fail never pass test-armhf-armhf-xl-cubietruck 13 saverestore-support-check fail never pass test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 13 saverestore-support-check fail never pass test-armhf-armhf-xl-credit2 13 saverestore-support-check fail never pass test-armhf-armhf-xl-vhd 11 migrate-support-check fail never pass test-armhf-armhf-xl-vhd 12 saverestore-support-check fail never pass test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail never pass test-armhf-armhf-libvirt-qcow2 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass version targeted for testing: xen 5bcf70dfaf71106970f6e256d2fe4e5158721ab6 baseline version: xen 3903db165ec9f823bfc0aca91e213c2cc221dc45 Last test of basis 101272 2016-10-05 05:20:26 Z 21 days Testing same since 101668 2016-10-25 15:55:01 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Dario Faggioli <dario.faggioli@xxxxxxxxxx> George Dunlap <george.dunlap@xxxxxxxxxx> Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Stefano Stabellini <sstabellini@xxxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64-xsm pass build-armhf-xsm pass build-i386-xsm pass build-amd64-xtf pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-prev pass build-i386-prev pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass build-amd64-rumprun pass build-i386-rumprun pass test-xtf-amd64-amd64-1 pass test-xtf-amd64-amd64-2 pass test-xtf-amd64-amd64-3 pass test-xtf-amd64-amd64-4 pass test-xtf-amd64-amd64-5 pass test-amd64-amd64-xl pass test-armhf-armhf-xl pass test-amd64-i386-xl pass test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemut-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-xsm pass test-armhf-armhf-libvirt-xsm pass test-amd64-i386-libvirt-xsm pass test-amd64-amd64-xl-xsm pass test-armhf-armhf-xl-xsm pass test-amd64-i386-xl-xsm pass test-amd64-amd64-qemuu-nested-amd fail test-amd64-amd64-xl-pvh-amd fail test-amd64-i386-qemut-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemut-debianhvm-amd64 pass test-amd64-i386-xl-qemut-debianhvm-amd64 pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-freebsd10-amd64 pass test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 pass test-amd64-amd64-rumprun-amd64 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-i386-xl-qemuu-win7-amd64 fail test-armhf-armhf-xl-arndale pass test-amd64-amd64-xl-credit2 pass test-armhf-armhf-xl-credit2 pass test-armhf-armhf-xl-cubietruck pass test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumprun-i386 pass test-amd64-amd64-qemuu-nested-intel pass test-amd64-amd64-xl-pvh-intel fail test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel fail test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt fail test-amd64-i386-libvirt pass test-amd64-amd64-migrupgrade pass test-amd64-i386-migrupgrade pass test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu pass test-amd64-amd64-pair fail test-amd64-i386-pair pass test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair pass test-amd64-amd64-amd64-pvgrub pass test-amd64-amd64-i386-pvgrub pass test-amd64-amd64-pygrub pass test-armhf-armhf-libvirt-qcow2 pass test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw pass test-amd64-i386-xl-raw pass test-amd64-amd64-xl-rtds pass test-armhf-armhf-xl-rtds fail test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass test-amd64-amd64-libvirt-vhd pass test-armhf-armhf-xl-vhd pass test-amd64-amd64-xl-qemut-winxpsp3 pass test-amd64-i386-xl-qemut-winxpsp3 pass test-amd64-amd64-xl-qemuu-winxpsp3 pass test-amd64-i386-xl-qemuu-winxpsp3 pass ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit 5bcf70dfaf71106970f6e256d2fe4e5158721ab6 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Oct 25 17:13:09 2016 +0200 x86: MISALIGNSSE feature depends on SSE Suggested-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Release-acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> master commit: b4ca886ab18ddcc729c1bc3d730ab078508d7ce3 master date: 2016-10-24 17:34:17 +0200 commit 013bced96898164de8ec8e66a3759e5316239ead Author: Stefano Stabellini <sstabellini@xxxxxxxxxx> Date: Tue Oct 25 17:12:52 2016 +0200 vscsiif.h: replace PAGE_SIZE with VSCSIIF_PAGE_SIZE Do not reference PAGE_SIZE directly: it could be undefined, or it could have different values in the frontend or in the backend. Define VSCSIIF_PAGE_SIZE as 4096, assuming all users of vscsiif.h have 4K page granularity. Replace PAGE_SIZE with VSCSIIF_PAGE_SIZE. Signed-off-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> Release-acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> master commit: d93539cc486aa6022195305dbea5fe12f90b69fe master date: 2016-10-21 09:58:16 +0100 commit ebb883c0f7a37c1cf5ad12fc254789f2beaa0661 Author: Stefano Stabellini <sstabellini@xxxxxxxxxx> Date: Tue Oct 25 17:12:33 2016 +0200 usbif.h: replace PAGE_SIZE with USBIF_RING_SIZE Do not reference PAGE_SIZE directly: it could be undefined, or it could have different values in the frontend or in the backend. Define USBIF_RING_SIZE as 4096, assuming all users of usbif.h have 4K page granularity. Replace PAGE_SIZE with USBIF_RING_SIZE. Signed-off-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> Release-acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> master commit: 04535bee06858fd949c743cfecc4d7b96333a16c master date: 2016-10-21 09:57:55 +0100 commit 37fd69415fb98f540932dc2ff15faaeb5d2cd95d Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Oct 25 17:12:05 2016 +0200 x86/Viridian: don't depend on undefined register state The high halves of all GPRs are undefined in 32-bit and compat modes, and the dependency is being obfuscated by our structure field names not matching architectural register names (it was actually while putting together a patch to correct this when I noticed the issue here). For consistency also use the architecturally correct names on the output side. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx> master commit: a709a3a646302e95ba42beac89264f6cdacd0c64 master date: 2016-10-14 14:09:42 +0200 commit 7bbea96bb81af670e3b6fb117791a475b3aa884f Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Oct 25 17:11:37 2016 +0200 x86emul: fix pushing of selector registers Both explicit PUSH and far CALL currently push unrelated data (the segment attributes word) in the high half (attributes and limit in the 64-bit case in the high 48 bits) instead of zero. To avoid having to apply this and further changes in multiple places, also fold the two (respectively) far call/jmp instances into one. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 373923ed9c2ed36925f574387db2be2ebe5ce45a master date: 2016-10-14 14:09:16 +0200 commit a91344a3142fea5e826ac8b3ef0b623699bf5f71 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Oct 25 17:11:08 2016 +0200 x86/hvm: Clobber %cs.L when LME becomes set Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: ed00f1761689ac7b9c074e9084c81e47c25d460c master date: 2016-10-14 12:44:29 +0100 commit 2b593c9a93a8256e2488a34858e914809c3cc49a Author: George Dunlap <george.dunlap@xxxxxxxxxx> Date: Tue Oct 25 17:10:42 2016 +0200 xen/trace: Fix trace metadata page count calculation (revert fbf96e6) Changeset fbf96e6, "xentrace: correct formula to calculate t_info_pages", broke the trace metadata page count calculation, by mistaking t_info_first_offset as denominated in bytes, when in fact it is denominated in words (uint32_t). Effectively revert that change, and put a comment there to reduce the chance that someone will make that mistake in the future. Reviewed-by: Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> Tested-by: Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxx> master commit: 71b8b46111219a2f83f4f9ae06ac5409744ea86e master date: 2016-10-11 14:23:52 +0100 commit 4b323ed7bba4b471cabec24a281e8cbdc4d74c23 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Oct 25 17:10:05 2016 +0200 x86: defer not-present segment checks Following on from commits 5602e74c60 ("x86emul: correct loading of %ss") and bdb860d01c ("x86/HVM: correct segment register loading during task switch") the point of the non-.present checks needs to be refined: #NP (and its #SS companion), other than suggested by the various instruction pages in Intel's SDM, gets checked for only after all type and permission checks. The only checks getting done even later are the long mode specific ones for system descriptors (which we don't support yet) and 64-bit code segments (i.e. anything touching other than the attribute byte). Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> x86/hvm: Correct the position of the %cs L/D checks Contrary to the description in the software manuals, in Long Mode, attempts to load %cs check that D is not set in combination with L before the present flag is checked. This can be observed because the L/D check fails with #GP before the presence check failes with #NP. This change partially reverts c/s 78ff18c90 "x86: defer not-present segment checks", taking it back to how it was in the v1 submission. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 78ff18c905318a9b1e5dd32662986f03b10a4e56 master date: 2016-10-10 12:16:49 +0200 master commit: 13b9f31751a55a96e86bd7e64b433a62a4a5b71e master date: 2016-10-14 12:43:17 +0100 commit c26fc22704aef21b9116d803fc1587a859b97b03 Author: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Date: Tue Oct 25 17:08:58 2016 +0200 xen: credit1: return the 'time remaining to the limit' as next timeslice. If vcpu x has run for 200us, and sched_ratelimit_us is 1000us, continue running x _but_ return 1000us-200us as the next time slice. This way, next scheduling point will happen in 800us, i.e., exactly at the point when x crosses the threshold, and can be descheduled (if appropriate). Right now (without this patch), we're always returning sched_ratelimit_us (1000us, in the example above), which means we're (potentially) allowing x to run more than it should have been able to. Note that, however, in order to avoid setting timers to very short intervals, which is part of the purpose of rate limiting, we never use a time slice smaller than a well defined threshold. Such threshold (CSCHED_MIN_TIMER defined in this patch) is, in general independent from rate limiting, but it looks a good idea to set it to the minimum possible ratelimiting value. Signed-off-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxx> master commit: 0053127890ebe9cafbd232752636a15881e4915a master date: 2016-09-30 14:46:36 +0100 (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |