[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable-smoke test] 107547: regressions - trouble: blocked/broken/fail/pass
flight 107547 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/107547/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf 4 host-build-prep fail REGR. vs. 107540 Tests which did not succeed, but are not blocking: test-armhf-armhf-xl 1 build-check(1) blocked n/a test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a build-arm64-pvops 5 kernel-build fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass version targeted for testing: xen f97838bbd980a0104e16c4a12fbf514f9fa805f1 baseline version: xen 5d1ad47ff7940d95c322667678a190c8607754b4 Last test of basis 107540 2017-04-19 12:02:20 Z 0 days Testing same since 107544 2017-04-19 17:03:35 Z 0 days 2 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Ross Lagerwall <ross.lagerwall@xxxxxxxxxx> jobs: build-amd64 pass build-armhf broken build-amd64-libvirt pass build-arm64-pvops fail test-armhf-armhf-xl blocked test-arm64-arm64-xl-xsm broken 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 Not pushing. ------------------------------------------------------------ commit f97838bbd980a0104e16c4a12fbf514f9fa805f1 Author: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx> Date: Tue Apr 18 16:47:24 2017 +0100 x86: Move microcode loading earlier Move microcode loading earlier for the boot CPU and secondary CPUs so that it takes place before identify_cpu() is called for each CPU. Without this, the detected features may be wrong if the new microcode loading adjusts the feature bits. That could mean that some fixes (e.g. d6e9f8d4f35d ("x86/vmx: fix vmentry failure with TSX bits in LBR")) don't work as expected. Previously during boot, the microcode loader was invoked for each secondary CPU started and then again for each CPU as part of an initcall. Simplify the code so that it is invoked exactly once for each CPU during boot. Signed-off-by: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Tested-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Release-acked-by: Julien Grall <julien.grall@xxxxxxx> (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 |