[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-unstable-smoke test] 159138: regressions - FAIL
flight 159138 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/159138/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-build fail REGR. vs. 159054 build-armhf 6 xen-build fail REGR. vs. 159054 Tests which did not succeed, but are not blocking: test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a test-armhf-armhf-xl 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 15 migrate-support-check fail never pass version targeted for testing: xen 25ee478662d378ec2b24f517fb6d8d4829b885ff baseline version: xen ca82d3fecc93745ee17850a609ac7772bd7c8bf7 Last test of basis 159054 2021-02-05 20:01:29 Z 2 days Testing same since 159138 2021-02-08 13:00:32 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> jobs: build-arm64-xsm fail build-amd64 pass build-armhf fail build-amd64-libvirt pass build-amd64-pvops pass build-arm64-pvops pass build-armhf-pvops pass test-armhf-armhf-xl blocked test-arm64-arm64-xl-xsm blocked test-amd64-amd64-xl-qemuu-debianhvm-amd64 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 25ee478662d378ec2b24f517fb6d8d4829b885ff Author: Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> Date: Wed Feb 3 20:07:04 2021 +0000 tools/libxl: only set viridian flags on new domains Domains migrating or restoring should have viridian HVM param key in the migration stream already and setting that twice results in Xen returing -EEXIST on the second attempt later (during migration stream parsing) in case the values don't match. That causes migration/restore operation to fail at destination side. That issue is now resurfaced by the latest commits (983524671 and 7e5cffcd1e) extending default viridian feature set making the values from the previous migration streams and those set at domain construction different. Suggested-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Signed-off-by: Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Release-Acked-by: Ian Jackson <iwj@xxxxxxxxxxxxxx> commit 804fe751375b1f40eb3142121bf2b70fa2a83972 Author: Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> Date: Wed Feb 3 20:07:03 2021 +0000 tools/libxl: pass libxl__domain_build_state to libxl__arch_domain_create No functional change. Signed-off-by: Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> Reviewed-by: Ian Jackson <iwj@xxxxxxxxxxxxxx> Release-Acked-by: Ian Jackson <iwj@xxxxxxxxxxxxxx> (qemu changes not included)
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |