[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable-smoke test] 134315: trouble: blocked/broken/pass
flight 134315 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/134315/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm <job status> broken build-arm64-xsm 4 host-install(4) broken REGR. vs. 133991 Tests which did not succeed, but are not blocking: test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 13 migrate-support-check fail never pass test-armhf-armhf-xl 13 migrate-support-check fail never pass test-armhf-armhf-xl 14 saverestore-support-check fail never pass version targeted for testing: xen 82a9e0aa193cacd9ae9fe37deff5de9ccd4212ad baseline version: xen cb70a26f78848fe45f593f7ebc9cfaac760a791b Last test of basis 133991 2019-03-22 15:00:46 Z 11 days Failing since 134068 2019-03-25 12:00:51 Z 8 days 37 attempts Testing same since 134307 2019-04-02 18:00:38 Z 0 days 3 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Christian Lindig <christian.lindig@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Juergen Gross <jgross@xxxxxxxx> Kevin Tian <kevin.tian@xxxxxxxxx> M A Young <m.a.young@xxxxxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-arm64-xsm broken build-amd64 pass build-armhf pass build-amd64-libvirt pass test-armhf-armhf-xl pass test-arm64-arm64-xl-xsm blocked test-amd64-amd64-xl-qemuu-debianhvm-i386 pass test-amd64-amd64-libvirt 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 broken-job build-arm64-xsm broken broken-step build-arm64-xsm host-install(4) Not pushing. ------------------------------------------------------------ commit 82a9e0aa193cacd9ae9fe37deff5de9ccd4212ad Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Mar 27 19:52:17 2019 +0000 x86/vvmx: Fix debug prints to not have 17 unnecessary spaces This has been problematic since its introduction in Xen 4.3 Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> commit a57a1b26ec0ae31f924cf2bbcf479637d007be44 Author: Wei Liu <wei.liu2@xxxxxxxxxx> Date: Mon Apr 1 11:32:38 2019 +0100 tools/ocaml: make python scripts 2 and 3 compatible 1. Explicitly import reduce because that's required in 3. 2. Change print to function. 3. Eliminate invocations of has_key. Signed-off-by: M A Young <m.a.young@xxxxxxxxxxxx> Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Christian Lindig <christian.lindig@xxxxxxxxxx> commit ff915c8cacc264ae1380d51fea07267b8308d7ba Author: Wei Liu <wei.liu2@xxxxxxxxxx> Date: Mon Apr 1 11:32:37 2019 +0100 pygrub: encode / decode string in Python 3 String is unicode in 3 but bytes in 2. We need to call encode / decode function when using Python 3. Reported-by: M A Young <m.a.young@xxxxxxxxxxxx> Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 767ba397d34848c7e0c4e9cdfc5efa4e0cb61442 Author: Wei Liu <wei.liu2@xxxxxxxxxx> Date: Mon Apr 1 11:32:36 2019 +0100 pygrub/grub: always use integer for default entry The original code set the default to either a string or an integer (0) and relies on a Python 2 specific behaviour to work (integer is allowed to be compared to string in Python 2 but not 3). Always use integer. The caller (pygrub) already has code to handle that. Reported-by: M A Young <m.a.young@xxxxxxxxxxxx> Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 485079e816788d70169f45579e1f5a8f909dc1b3 Author: Wei Liu <wei.liu2@xxxxxxxxxx> Date: Mon Apr 1 11:32:35 2019 +0100 pygrub: fix message in grub parser The code suggests 0 is allowed. Zero is not a positive number. Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 905d7340f6d0abfbf986cede6e535c51ab1de3c3 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Mon Apr 1 10:08:43 2019 +0000 xen/sched: Remove d->is_pinned The is_pinned field is rather odd. It can only be activated with the "dom0_vcpus_pin" command line option, and causes dom0 (or the late hwdom) to have its vcpus identity pinned to pcpus. Having dom0_vcpus_pin active disallows the use of vcpu_set_hard_affinity(). However, when a pcpu is offlined, or moved between cpupools, the affinity is broken and reverts to cpumask_all. This results in vcpus which are no longer pinned, and cannot be adjusted. A related bit of functionality is the is_pinned_vcpu() predicate. This is only used by x86 code, and permits the use of VCPUOP_get_physid and writeable access to some extra MSRs. The implementation however returns true for is_pinned (which will include unpinned vcpus from the above scenario), *or* if the hard affinity mask only has a single bit set (which is redundant with the intended effect of is_pinned, but also includes other domains). Rework the behaviour of "dom0_vcpus_pin" to only being an initial pinning configuration, and permit full adjustment. This allows the user to reconfigure dom0 after the fact or fix up from the fallout of cpu hot unplug and cpupool manipulation. An unprivileged domain has no business using VCPUOP_get_physid, and shouldn't be able to just because it happens to be pinned by admin choice. All uses of is_pinned_vcpu() should be restricted to the hardware domain, so rename it to is_hwdom_pinned_vcpu() to avoid future misuse. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Dario Faggioli <dfaggioli@xxxxxxxx> commit d96a4d6c9cb57bdc46501880c908ae85197243da Author: Wei Liu <wei.liu2@xxxxxxxxxx> Date: Mon Apr 1 11:39:00 2019 +0100 tools/xenmon: make xenmon.py compatible with python 2 and 3 Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit c37db16ccb3426e2d22ec7731649770b56984b27 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Mon Apr 1 11:12:54 2019 +0200 x86/APIC: suppress redundant "Switched to ..." messages There's no need to log anything when what we "switch to" is what is in use already. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit f68f35fd2016e36ee30f8b3e7dfd46c554407ac1 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Mon Apr 1 11:12:16 2019 +0200 x86emul/fuzz: adjust canonicalization in sanitize_input() Drop it entirely for %rbp - this register is not special purpose enough to warrant such special treatment. Add a comment to clarify the purpose of the canonicalization of %rip and %rsp. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 7881bf488263f52b8f6dd9935031d7b405958c0c Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Mon Apr 1 11:09:43 2019 +0200 x86/paging: paging_set_allocation() is init-only This is needed for Dom0 creation only, therefore it gets additionally framed by an #ifdef. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxx> commit 12381e20b5c2cb2f54601bef47c4f6e43acf3833 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri Mar 29 13:32:09 2019 +0000 xen/timers: Document and improve the representation of the timer heap metadata The {GET,SET}_HEAP_{SIZE,LIMIT}() macros implement some completely undocumented pointer misuse to store the size and limit information. In practice, heap[0] is never a timer pointer, and used to stash the metadata instead. Extend the HEAP OPERATIONS comment to include this detail. Introduce a structure representing the heap metadata, and a static inline function to perfom the type punning. Replace all of the above macros with an equivelent expression involving the heap_metadata() helper. Note that I deliberately haven't rearranged the surrounding code - this allows the correctness of the transformation to be checked by confirming that the compiled binary is identical. This also removes two cases of a macro argument with side effects, which only worked correctly because the arguments were only evaluated once. Finally, fix up the type of dummy_heap. The old code functioned correctly, but only by virtue of confusing a discrete object and a single-entry array. Change its type to match the intended semantics, and drop the redundant initialisation in timer_init(). No functional change. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 753ba43d6d16e688f688e01e1c77463ea2c6ec9f Author: Juergen Gross <jgross@xxxxxxxx> Date: Thu Mar 28 16:46:22 2019 +0100 xen/sched: fix credit2 smt idle handling Credit2's smt_idle_mask_set() and smt_idle_mask_clear() are used to identify idle cores where vcpus can be moved to. A core is thought to be idle when all siblings are known to have the idle vcpu running on them. Unfortunately the information of a vcpu running on a cpu is per runqueue. So in case not all siblings are in the same runqueue a core will never be regarded to be idle, as the sibling not in the runqueue is never known to run the idle vcpu. Use a credit2 specific cpumask of siblings with only those cpus being marked which are in the same runqueue as the cpu in question. Signed-off-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Dario Faggioli <dfaggioli@xxxxxxxx> commit e88afede8cbc18032bcab49b3a25b472d5516cf5 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Jul 10 13:53:21 2018 +0100 libx86: Recalculate synthesised cpuid_policy fields when appropriate When filling a policy, either from CPUID or an incomming leaf stream, recalculate the synthesised vendor value. All callers are expected to want this behaviour. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 1c2c9f85dd36bd908441b37ab73172358509c9b5 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Mar 20 14:56:15 2019 +0000 tools/libxc: Use x86_cpuid_lookup_vendor() rather than opencoding the logic This doesn't address any of the assumptions that "anything which isn't AMD is Intel". This logic is expected to be replaced wholesale with libx86 in the longterm. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 00b4f4d0fb75dc183b499e78d1abcb865dbc30d7 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Jul 10 13:53:21 2018 +0100 x86/cpuid: Drop get_cpu_vendor() completely get_cpu_vendor() tries to do a number of things, and ends up doing none of them well. For calculating the vendor itself, use x86_cpuid_lookup_vendor() which is implemented in a far more efficient manner than looping over cpu_devs[]. For setting up this_cpu, set it up once on the BSP only, rather than latest-takes-precident across the APs. Such a system is probably not going to boot, but this feels like a less dangerous course of action. Adjust the printed errors to be more clear in the mismatch case. This removes the only user of cpu_dev->c_ident[], so drop that field as well. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit e72309ffbe7c4e507649c74749f130cda691131c Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Mar 20 14:05:11 2019 +0000 libx86: Introduce x86_cpuid_lookup_vendor() Also introduce constants for the vendor strings in CPUID leaf 0. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 8eed571409a7f81ec9327cfa95d7c298333e22e4 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Mar 26 14:23:03 2019 +0000 CI: Add a CentOS 6 container and build jobs CentOS 6 is probably the most frequently broken build, so adding it to CI would be a very good move. One problem is that CentOS 6 comes with Python 2.6, and Qemu requires 2.7. There appear to be no sensible ways to get Python 2.7 into a CentOS 6 environments, so modify the build script to skip the Qemu upstream build instead. Additionally, SeaBIOS requires GCC 4.6 or later, so skip it as well. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit 1316369dca610352cce3aaf76e90db1cce75ed9f Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri Mar 22 11:12:28 2019 +0000 CI: Fix indentation in containerize script The script is mostly indented with spaces, but there are three tabs. Fix them up to be consistent. No functional change. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |