|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable test] 100470: regressions - FAIL
flight 100470 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/100470/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail REGR. vs. 100431 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds 15 guest-start/debian.repeat fail REGR. vs. 100431 build-amd64-rumpuserxen 6 xen-build fail like 100431 build-i386-rumpuserxen 6 xen-build fail like 100431 test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 100431 test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail like 100431 test-amd64-amd64-xl-rtds 9 debian-install fail like 100431 test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 100431 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 100431 Tests which did not succeed, but are not blocking: test-amd64-i386-rumpuserxen-i386 1 build-check(1) blocked n/a test-amd64-amd64-rumpuserxen-amd64 1 build-check(1) blocked n/a 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-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-libvirt-vhd 11 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-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-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-xsm 13 saverestore-support-check fail never pass test-armhf-armhf-xl-xsm 12 migrate-support-check fail never pass test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 14 guest-saverestore fail never pass test-armhf-armhf-libvirt 14 guest-saverestore fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 13 guest-saverestore fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-qcow2 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-qcow2 13 guest-saverestore 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-armhf-armhf-xl-multivcpu 13 saverestore-support-check fail never pass test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 13 saverestore-support-check fail never pass test-armhf-armhf-xl-rtds 12 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 13 saverestore-support-check fail never pass test-armhf-armhf-xl-credit2 12 migrate-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 version targeted for testing: xen a55ad65d3a30d5b3a026a7481ce05f28065920f0 baseline version: xen 072e6709978143145a1c1b98c7f014dc4d87907f Last test of basis 100431 2016-08-12 07:34:23 Z 0 days Failing since 100466 2016-08-12 15:15:07 Z 0 days 2 attempts Testing same since 100470 2016-08-12 23:44:27 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Tamas K Lengyel <tamas@xxxxxxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64-xsm pass build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-oldkern pass build-i386-oldkern pass build-amd64-prev pass build-i386-prev pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass build-amd64-rumpuserxen fail build-i386-rumpuserxen fail 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 fail 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-rumpuserxen-amd64 blocked 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 fail test-armhf-armhf-xl-cubietruck pass test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumpuserxen-i386 blocked 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 pass 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 pass 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 fail test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw fail test-amd64-i386-xl-raw pass test-amd64-amd64-xl-rtds fail 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 a55ad65d3a30d5b3a026a7481ce05f28065920f0 Author: Wei Liu <wei.liu2@xxxxxxxxxx> Date: Fri Aug 12 16:23:33 2016 +0100 Config.mk: update mini-os commit Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit c0bc0adf24d6991fad29aa788382d3533b532174 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Aug 12 16:57:32 2016 +0200 x86emul: use DstEax where possible While it avoids just a few instructions, we should nevertheless make use of generic code as much as possible. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 989cdfa9b484c2c2eb41f779fa6df7fd29a00e81 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Aug 12 16:57:07 2016 +0200 x86emul: don't special case fetching unsigned 8-bit immediates These can be made work using SrcImmByte, making sure the low 8 bits of src.val get suitably zero extended upon consumption. SHLD and SHRD require a little more adjustment: Their source operands get changed away from SrcReg, handling the register access "manually" instead of the insn byte fetching. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 3c71d160677fa4f4b769f33fe201ecd9219ab234 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Aug 12 16:55:48 2016 +0200 x86emul: all push flavors are data moves Make all paths leading to the "push" label have the Mov flag set, and ASSERT() that to be the case. For the opcode FF group the adjustment is benign for the paths not leading to "push", as they all set dst.type to OP_NONE Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit a3227edc20108e120021caccb9f79ca6741ffb9e Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Aug 12 16:55:13 2016 +0200 x86emul: don't special case fetching immediates of near and short branches These immediates follow the standard patterns in all modes, so they're better fetched by the generic source operand handling code. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 848d8eee52c1122c13dc2f76431a83720cd9267d Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Aug 12 16:54:24 2016 +0200 x86emul: don't special case fetching the immediate of PUSH These immediates follow the standard patterns in all modes, so they're better fetched by the generic source operand handling code. To facilitate testing, instead of adding yet another of these pretty convoluted individual test cases, simply introduce another blowfish run with -mno-accumulate-outgoing-args (the additional -Dstatic is to keep the compiler from converting the calling convention to "regparm(3)", which I did observe it does). To make this introduction of a new blowfish pass (and potential further ones later one) have less impact on the readability of the final code, abstract all such "binary blob" executions via a table to iterate through. The resulting native code execution adjustment also uncovered a lack of clobbers on the asm() in the 64-bit case, which is being fixed at once. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit cbfe4db8d750f3efdd11d482934b1cbfbe4284e6 Author: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Date: Fri Aug 12 16:51:36 2016 +0200 vm_event: synchronize vCPU state in vm_event_resume() Vm_event_vcpu_pause() needs to use vcpu_pause_nosync() in order for the current vCPU to not get stuck. A consequence of this is that the custom vm_event response handlers will not always see the real vCPU state in v->arch.user_regs. This patch makes sure that the state is always synchronized in vm_event_resume, before any handlers have been called. This problem especially affects vm_event_set_registers(). Simply checking vm_event_pause_count to make sure the vCPU is paused suffices since there's only one ring / consumer at a time, and events are being processed one-by-one, so the toolstack won't unpause the vCPU behind our backs. Signed-off-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Acked-by: Tamas K Lengyel <tamas@xxxxxxxxxxxxx> commit e567d6942544585d8ca1eeec16a5c63c956e5dbc Author: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Date: Fri Aug 12 16:51:21 2016 +0200 vm_event: fix comment There's no such thing as function vm_event_wake_waiters() anymore. Signed-off-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> commit 20aa9381db781ee050355635efd14a9a37e1d94d Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Thu Aug 11 17:21:14 2016 +0000 x86/cpufreq: Avoid using processor_pminfo[cpu] when it is NULL The undefined behaviour sanitiser shows that it really is NULL via the pre_initcall path. (XEN) ================================================================================ (XEN) UBSAN: Undefined behaviour in cpufreq.c:158:66 (XEN) member access within null pointer of type 'struct processor_pminfo' (XEN) ----[ Xen-4.8-unstable x86_64 debug=y Not tainted ]---- <snip> (XEN) [<ffff82d0801c4231>] cpufreq_add_cpu+0x161/0xdc0 (XEN) [<ffff82d0801c6610>] cpufreq.c#cpu_callback+0x20/0x30 (XEN) [<ffff82d0804eefad>] cpufreq.c#cpufreq_presmp_init+0x2d/0x50 (XEN) [<ffff82d0804c5942>] do_presmp_initcalls+0x22/0x30 (XEN) [<ffff82d08051852d>] __start_xen+0x378d/0x42f0 (XEN) [<ffff82d080100073>] __high_start+0x53/0x60 Fix two other occurances of the same buggy logic. The processor_pminfo[] objects are only allocated as a result of XENPF_set_processor_pminfo hypercalls, which means that this early cpu callback will always hit the early NULL check, and is therefore pointless. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 5d8f8fa902685f4cceaf9e2b75da3c846956c2cd Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Thu Aug 11 16:32:10 2016 +0000 x86/boot: Align e820 and video data in the boot trampoline The undefined behaviour sanitiser in Clang 3.8 identifies that these are all misaigned when used in __start_xen(). Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> (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 |