* [libvirt test] 176276: trouble: blocked/broken/pass
@ 2023-01-30 17:32 osstest service owner
0 siblings, 0 replies; only message in thread
From: osstest service owner @ 2023-01-30 17:32 UTC (permalink / raw)
To: xen-devel
flight 176276 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/176276/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf <job status> broken
build-armhf 4 host-install(4) broken REGR. vs. 176139
build-armhf 3 syslog-server running
Tests which did not succeed, but are not blocking:
build-armhf-libvirt 1 build-check(1) blocked n/a
test-armhf-armhf-libvirt-raw 1 build-check(1) blocked n/a
test-armhf-armhf-libvirt 1 build-check(1) blocked n/a
test-armhf-armhf-libvirt-qcow2 1 build-check(1) blocked n/a
build-armhf 5 capture-logs broken blocked in 176139
test-amd64-amd64-libvirt 15 migrate-support-check fail never pass
test-amd64-i386-libvirt 15 migrate-support-check fail never pass
test-amd64-i386-libvirt-xsm 15 migrate-support-check fail never pass
test-amd64-amd64-libvirt-xsm 15 migrate-support-check fail never pass
test-arm64-arm64-libvirt-xsm 15 migrate-support-check fail never pass
test-arm64-arm64-libvirt-xsm 16 saverestore-support-check fail never pass
test-arm64-arm64-libvirt 15 migrate-support-check fail never pass
test-arm64-arm64-libvirt 16 saverestore-support-check fail never pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 13 migrate-support-check fail never pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 13 migrate-support-check fail never pass
test-arm64-arm64-libvirt-qcow2 14 migrate-support-check fail never pass
test-arm64-arm64-libvirt-qcow2 15 saverestore-support-check fail never pass
test-arm64-arm64-libvirt-raw 14 migrate-support-check fail never pass
test-arm64-arm64-libvirt-raw 15 saverestore-support-check fail never pass
test-amd64-i386-libvirt-raw 14 migrate-support-check fail never pass
test-amd64-amd64-libvirt-vhd 14 migrate-support-check fail never pass
version targeted for testing:
libvirt 9f8fba7501327a60f6adb279ea17f0e2276071be
baseline version:
libvirt 95a278a84591b6a4cfa170eba31c8ec60e82f940
Last test of basis 176139 2023-01-26 04:18:49 Z 4 days
Failing since 176233 2023-01-27 04:18:53 Z 3 days 4 attempts
Testing same since 176262 2023-01-28 04:20:25 Z 2 days 3 attempts
------------------------------------------------------------
People who touched revisions under test:
Jiri Denemark <jdenemar@redhat.com>
Martin Kletzander <mkletzan@redhat.com>
Michal Privoznik <mprivozn@redhat.com>
jobs:
build-amd64-xsm pass
build-arm64-xsm pass
build-i386-xsm pass
build-amd64 pass
build-arm64 pass
build-armhf broken
build-i386 pass
build-amd64-libvirt pass
build-arm64-libvirt pass
build-armhf-libvirt blocked
build-i386-libvirt pass
build-amd64-pvops pass
build-arm64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-xsm pass
test-arm64-arm64-libvirt-xsm pass
test-amd64-i386-libvirt-xsm pass
test-amd64-amd64-libvirt pass
test-arm64-arm64-libvirt pass
test-armhf-armhf-libvirt blocked
test-amd64-i386-libvirt pass
test-amd64-amd64-libvirt-pair pass
test-amd64-i386-libvirt-pair pass
test-arm64-arm64-libvirt-qcow2 pass
test-armhf-armhf-libvirt-qcow2 blocked
test-arm64-arm64-libvirt-raw pass
test-armhf-armhf-libvirt-raw blocked
test-amd64-i386-libvirt-raw pass
test-amd64-amd64-libvirt-vhd 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 build-armhf broken
broken-step build-armhf capture-logs
broken-step build-armhf host-install(4)
Not pushing.
------------------------------------------------------------
commit 9f8fba7501327a60f6adb279ea17f0e2276071be
Author: Jiri Denemark <jdenemar@redhat.com>
Date: Thu Jan 26 16:12:00 2023 +0100
remote: Fix version annotation for remoteDomainFDAssociate
The API was added in libvirt 9.0.0.
Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
commit a0fbf1e25cd0f91bedf159bf7f0086f4b1aeafc2
Author: Michal Privoznik <mprivozn@redhat.com>
Date: Thu Jan 26 16:48:50 2023 +0100
rpc: Use struct zero initializer for args
In a recent commit of v9.0.0-104-g0211e430a8 I've turned all args
vars in src/remote/remote_driver.c to be initialized wit {0}.
What I've missed was the generated code.
Do what we've done in v9.0.0-13-g1c656836e3 and init also args,
not just ret.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
commit 2dde3840b1d50e79f6b8161820fff9fe62f613a9
Author: Martin Kletzander <mkletzan@redhat.com>
Date: Thu Jan 26 16:57:20 2023 +0100
qemuxml2argvdata: Fix missing device in crypto-builtin XML
Another forgotten fix after a post-review rebase.
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
commit f3c9cbc36cc10775f6cefeb7e3de2f799dc74d70
Author: Martin Kletzander <mkletzan@redhat.com>
Date: Thu Jan 26 16:57:20 2023 +0100
qemuxml2argvdata: Fix watchdog parameters in crypto-builtin
Forgotten fix after a post-review rebase.
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
commit a2c5c5dad2275414e325ca79778fad2612d14470
Author: Martin Kletzander <mkletzan@redhat.com>
Date: Fri Jan 20 18:22:34 2023 +0100
news: Add information about iTCO watchdog changes
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
commit 2fa92efe9b286ad064833cd2d8b907698e58e1cf
Author: Martin Kletzander <mkletzan@redhat.com>
Date: Fri Jan 20 18:22:30 2023 +0100
Document change to multiple watchdogs
With the reasoning behind it.
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
commit 926594dcc82b40f483010cebe5addbf1d7f58b24
Author: Martin Kletzander <mkletzan@redhat.com>
Date: Fri Jan 20 11:22:22 2023 +0100
qemu: Add implicit watchdog for q35 machine types
The iTCO watchdog is part of the q35 machine type since its inception,
we just did not add it implicitly.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2137346
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
commit d81a27b9815d68d85d2ddc9671649923ee5905d7
Author: Martin Kletzander <mkletzan@redhat.com>
Date: Fri Jan 20 14:15:06 2023 +0100
qemu: Enable iTCO watchdog by disabling its noreboot pin strap
In order for the iTCO watchdog to be operational we must disable the
noreboot pin strap in qemu. This is the default starting from 8.0
machine types, but desirable for older ones as well. And we can safely
do that since that is not guest-visible.
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
commit 5b80e93e42a1d89ee64420debd2b4b785a144c40
Author: Martin Kletzander <mkletzan@redhat.com>
Date: Fri Jan 20 10:26:21 2023 +0100
Add iTCO watchdog support
Supported only with q35 machine types.
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
commit 1c61bd718a9e311016da799a42dfae18f538385a
Author: Martin Kletzander <mkletzan@redhat.com>
Date: Tue Nov 8 09:10:57 2022 +0100
Support multiple watchdog devices
This is already possible with qemu, and actually already happening with
q35 machines and a specified watchdog since q35 already includes a
watchdog we do not include in the XML. In order to express such
posibility multiple watchdogs need to be supported.
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
commit c5340d5420012412ea298f0102cc7f113e87d89b
Author: Martin Kletzander <mkletzan@redhat.com>
Date: Fri Jan 20 10:28:52 2023 +0100
qemuDomainAttachWatchdog: Avoid unnecessary nesting
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
commit 1cf7e6ec057a80f3c256d739a8228e04b7fb8862
Author: Jiri Denemark <jdenemar@redhat.com>
Date: Wed Jan 25 15:25:06 2023 +0100
remote: Drop useless cleanup in remoteDispatchNodeGet{CPU,Memory}Stats
The function cannot fail once it starts populating
ret->params.params_val[i].field.
Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
commit d0f339170f35957e7541e5b20552d0007e150fbc
Author: Jiri Denemark <jdenemar@redhat.com>
Date: Wed Jan 25 15:06:33 2023 +0100
remote: Avoid leaking uri_out
In case the API returned success and a NULL pointer in uri_out, we would
leak the preallocated buffer used for storing the uri_out pointer.
Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
commit 4849eb2220fb2171e88e014a8e63018d20a8de95
Author: Jiri Denemark <jdenemar@redhat.com>
Date: Wed Jan 25 11:56:28 2023 +0100
remote: Propagate error from virDomainGetSecurityLabelList via RPC
The daemon side of this API has been broken ever since the API was
introduced in 2012. Instead of sending the error from
virDomainGetSecurityLabelList via RPC so that the client can see it, the
dispatcher would just send a successful reply with return value set to
-1 (and an empty array of labels). The client side would propagate this
return value so the client can see the API failed, but the original
error would be lost.
Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
commit 0211e430a87a96db9a4e085e12f33caad9167653
Author: Michal Privoznik <mprivozn@redhat.com>
Date: Thu Jan 26 13:19:31 2023 +0100
remote: Initialize args variable
Recently, in v9.0.0-7-gb2034bb04c we've dropped initialization of
@args variable. The reasoning was that eventually, all members of
the variable will be set. Well, this is not correct. For
instance, in remoteConnectGetAllDomainStats() the
args.doms.doms_val pointer is set iff @ndoms != 0. However,
regardless of that, the pointer is then passed to VIR_FREE().
Worse, the whole args is passed to
xdr_remote_connect_get_all_domain_stats_args() which then calls
xdr_array, which tests the (uninitialized) pointer against NULL.
This effectively reverts b2034bb04c61c75ddbfbed46879d641b6f8ca8dc.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
commit c3afde9211b550d3900edc5386ab121f5b39fd3e
Author: Michal Privoznik <mprivozn@redhat.com>
Date: Thu Jan 26 11:56:10 2023 +0100
qemu_domain: Don't unref NULL hash table in qemuDomainRefreshStatsSchema()
The g_hash_table_unref() function does not accept NULL. Passing
NULL results in a glib warning being triggered. Check whether the
hash table is not NULL and unref it only then.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-01-30 17:33 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-30 17:32 [libvirt test] 176276: trouble: blocked/broken/pass osstest service owner
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.