* [xen-unstable-smoke test] 180072: regressions - trouble: fail/pass/starved
@ 2023-03-30 21:59 osstest service owner
0 siblings, 0 replies; only message in thread
From: osstest service owner @ 2023-03-30 21:59 UTC (permalink / raw
To: xen-devel
flight 180072 xen-unstable-smoke real [real]
flight 180075 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/180072/
http://logs.test-lab.xenproject.org/osstest/logs/180075/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt 8 xen-boot fail REGR. vs. 180068
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 15 migrate-support-check fail never pass
test-arm64-arm64-xl-xsm 16 saverestore-support-check fail never pass
test-armhf-armhf-xl 1 build-check(1) starved n/a
build-armhf 2 hosts-allocate starved n/a
version targeted for testing:
xen 64c21916167e6269280929fab1202537b54b13cf
baseline version:
xen 12c5eea3ca6fa2674726d62cc9f369f81861d23f
Last test of basis 180068 2023-03-30 16:01:56 Z 0 days
Testing same since 180072 2023-03-30 20:00:24 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Ayan Kumar Halder <ayan.kumar.halder@amd.com>
Julien Grall <jgrall@amazon.com>
jobs:
build-arm64-xsm pass
build-amd64 pass
build-armhf starved
build-amd64-libvirt pass
test-armhf-armhf-xl starved
test-arm64-arm64-xl-xsm pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass
test-amd64-amd64-libvirt fail
------------------------------------------------------------
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 64c21916167e6269280929fab1202537b54b13cf
Author: Ayan Kumar Halder <ayan.kumar.halder@amd.com>
Date: Tue Mar 21 14:03:47 2023 +0000
xen/arm: Use the correct format specifier
1. One should use 'PRIpaddr' to display 'paddr_t' variables. However,
while creating nodes in fdt, the address (if present in the node name)
should be represented using 'PRIx64'. This is to be in conformance
with the following rule present in https://elinux.org/Device_Tree_Linux
. node names
"unit-address does not have leading zeros"
As 'PRIpaddr' introduces leading zeros, we cannot use it.
So, we have introduced a wrapper ie domain_fdt_begin_node() which will
represent physical address using 'PRIx64'.
2. One should use 'PRIx64' to display 'u64' in hex format. The current
use of 'PRIpaddr' for printing PTE is buggy as this is not a physical
address.
Signed-off-by: Ayan Kumar Halder <ayan.kumar.halder@amd.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Acked-by: Julien Grall <jgrall@amazon.com>
(qemu changes not included)
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-03-30 21:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-03-30 21:59 [xen-unstable-smoke test] 180072: regressions - trouble: fail/pass/starved osstest service owner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).