[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xtf test] 131921: trouble: broken/pass
flight 131921 xtf real [real] http://logs.test-lab.xenproject.org/osstest/logs/131921/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-xtf-amd64-amd64-3 <job status> broken test-xtf-amd64-amd64-3 4 host-install(4) broken REGR. vs. 130526 version targeted for testing: xtf 2dc1902e6756163ceb1f079bede9c047725a7097 baseline version: xtf f9894eb67e7e472a648a1aae0de56ad940ca48ac Last test of basis 130526 2018-11-19 16:42:37 Z 53 days Testing same since 131921 2019-01-11 17:41:14 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Jan Beulich <jbeulich@xxxxxxxx> jobs: build-amd64-xtf pass build-amd64 pass build-amd64-pvops pass test-xtf-amd64-amd64-1 pass test-xtf-amd64-amd64-2 pass test-xtf-amd64-amd64-3 broken test-xtf-amd64-amd64-4 pass test-xtf-amd64-amd64-5 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 test-xtf-amd64-amd64-3 broken broken-step test-xtf-amd64-amd64-3 host-install(4) Not pushing. ------------------------------------------------------------ commit 2dc1902e6756163ceb1f079bede9c047725a7097 Author: Jan Beulich <JBeulich@xxxxxxxx> Date: Fri Jan 11 02:50:20 2019 -0700 nested-vmx: exceptions take priority over VMFail* The way the instruction invocations are coded, it is compiler version dependent whether things work: With old gcc, fail_{,in}valid will not get touched and hence remain at their initial values, while with newer gcc evaluation of the status flags occurs outside of the asm(), i.e. also when an exception was received (in which case EFLAGS didn't change from its value before the faulting instruction). Since it is more logical anyway to check for a possible exception first, do so uniformly instead of trying to fiddle with the asm() in some way. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/osstest-output
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |