flight 146828 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/146828/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 <job status> broken
build-arm64-xsm <job status> broken
build-armhf <job status> broken
build-amd64 4 host-install(4) broken REGR. vs. 146767
build-arm64-xsm 4 host-install(4) broken REGR. vs. 146767
build-armhf 4 host-install(4) broken REGR. vs. 146767
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 1 build-check(1) blocked n/a
build-amd64-libvirt 1 build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-debianhvm-amd64 1 build-check(1) blocked n/a
version targeted for testing:
xen 0a9c44486b901dbcef7c5e583d1a5ffbf4762bc5
baseline version:
xen 72dbcf0c065037dddb591a072c4f8f16fe888ea8
Last test of basis 146767 2020-02-06 17:01:03 Z 3 days
Failing since 146806 2020-02-08 13:00:53 Z 2 days 9 attempts
Testing same since 146828 2020-02-10 11:00:49 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.coop...@citrix.com>
Jan Beulich <jbeul...@suse.com>
Jeff Kubascik <jeff.kubas...@dornerworks.com>
Julien Grall <jgr...@amazon.com>
Julien Grall <jul...@xen.org>
Marek Marczykowski-Górecki <marma...@invisiblethingslab.com>
Wei Liu <w...@xen.org>
jobs:
build-arm64-xsm broken
build-amd64 broken
build-armhf broken
build-amd64-libvirt blocked
test-armhf-armhf-xl blocked
test-arm64-arm64-xl-xsm blocked
test-amd64-amd64-xl-qemuu-debianhvm-amd64 blocked
test-amd64-amd64-libvirt blocked
------------------------------------------------------------
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-amd64 broken
broken-job build-arm64-xsm broken
broken-job build-armhf broken
broken-step build-amd64 host-install(4)
broken-step build-arm64-xsm host-install(4)
broken-step build-armhf host-install(4)
Not pushing.
------------------------------------------------------------
commit 0a9c44486b901dbcef7c5e583d1a5ffbf4762bc5
Author: Andrew Cooper <andrew.coop...@citrix.com>
Date: Wed Feb 5 16:50:53 2020 +0000
tools/python: Drop cpuid helpers
These are believed-unused, and the underlying infrastructure is about to be
rewritten completely.
Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
Acked-by: Marek Marczykowski-Górecki <marma...@invisiblethingslab.com>
commit 69da7d5440c609c57c5bba9a73b91c62ba2852e6
Author: Jeff Kubascik <jeff.kubas...@dornerworks.com>
Date: Tue Feb 4 14:51:50 2020 -0500
xen/arm: Handle unimplemented VGICv3 registers as RAZ/WI
Per the ARM Generic Interrupt Controller Architecture Specification (ARM
IHI 0069E), reserved registers should generally be treated as RAZ/WI.
To simplify the VGICv3 design and improve guest compatibility, treat the
default case for GICD and GICR registers as read_as_zero/write_ignore.
Signed-off-by: Jeff Kubascik <jeff.kubas...@dornerworks.com>
Acked-by: Julien Grall <jul...@xen.org>
commit cbd1a54f6dea3f4a7feed51e189ebae50ac9dd15
Author: Julien Grall <jgr...@amazon.com>
Date: Tue Feb 4 16:53:49 2020 +0000
xen/include: Fix typoes in asm-x86/domain.h
Signed-off-by: Julien Grall <jgr...@amazon.com>
Acked-by: Andrew Cooper <andrew.coop...@citrix.com>
commit 24ea7abcdc8654ad2d9831a79c6d6f580aca6a3c
Author: Julien Grall <jgr...@amazon.com>
Date: Thu Feb 6 15:41:18 2020 +0000
xen/include: public: Document the padding in struct xen_hvm_param
There is an implicit padding of 2 bytes in struct xen_hvm_param between
the field domid and index. Make it explicit by introduce a padding
field. This can also serve as documentation.
Note that I don't think we can mandate it to be zero because a guest may
not have initialized the padding.
Signed-off-by: Julien Grall <jgr...@amazon.com>
Acked-by: Jan Beulich <jbeul...@suse.com>
Acked-by: Wei Liu <w...@xen.org>
(qemu changes not included)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
