* [Xen-devel] [libvirt test] 142904: regressions - FAIL
@ 2019-10-20 4:00 osstest service owner
0 siblings, 0 replies; only message in thread
From: osstest service owner @ 2019-10-20 4:00 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 142904 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142904/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-qcow2 15 guest-start/debian.repeat fail REGR. vs. 142840
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 saverestore-support-check fail like 142840
test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 142840
test-amd64-amd64-libvirt 13 migrate-support-check fail never pass
test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass
test-amd64-i386-libvirt 13 migrate-support-check fail never pass
test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
test-arm64-arm64-libvirt 13 migrate-support-check fail never pass
test-arm64-arm64-libvirt 14 saverestore-support-check fail never pass
test-arm64-arm64-libvirt-xsm 13 migrate-support-check fail never pass
test-arm64-arm64-libvirt-xsm 14 saverestore-support-check fail never pass
test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass
test-arm64-arm64-libvirt-qcow2 12 migrate-support-check fail never pass
test-arm64-arm64-libvirt-qcow2 13 saverestore-support-check fail never pass
test-armhf-armhf-libvirt 13 migrate-support-check fail never pass
test-armhf-armhf-libvirt-raw 12 migrate-support-check fail never pass
version targeted for testing:
libvirt 313a71ee7b424126a4507b12335fd77b51dab433
baseline version:
libvirt b83884d1a0f422e8147a7d1a39ccec0e0cca3285
Last test of basis 142840 2019-10-17 15:43:16 Z 2 days
Failing since 142862 2019-10-18 07:07:12 Z 1 days 2 attempts
Testing same since 142904 2019-10-19 04:18:49 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Cole Robinson <crobinso@redhat.com>
Daniel Henrique Barboza <danielhb413@gmail.com>
Daniel P. Berrangé <berrange@redhat.com>
Julio Faracco <jcfaracco@gmail.com>
Malina Salina <malina.salina@protonmail.com>
Michal Privoznik <mprivozn@redhat.com>
Peter Krempa <pkrempa@redhat.com>
jobs:
build-amd64-xsm pass
build-arm64-xsm pass
build-i386-xsm pass
build-amd64 pass
build-arm64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-arm64-libvirt pass
build-armhf-libvirt pass
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 pass
test-amd64-i386-libvirt pass
test-amd64-amd64-libvirt-pair pass
test-amd64-i386-libvirt-pair pass
test-arm64-arm64-libvirt-qcow2 fail
test-armhf-armhf-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
Not pushing.
------------------------------------------------------------
commit 313a71ee7b424126a4507b12335fd77b51dab433
Author: Malina Salina <malina.salina@protonmail.com>
Date: Fri Sep 27 17:10:34 2019 +0100
network: allow DHCP/DNS/TFTP explicitly in OUTPUT rules
While the default iptables setup used by Fedora/RHEL distros
only restricts traffic on the INPUT and/or FORWARD rules,
some users might have custom firewalls that restrict the
OUTPUT rules too.
These can prevent DHCP/DNS/TFTP responses from dnsmasq
from reaching the guest VMs. We should thus whitelist
these protocols in the OUTPUT chain, as well as the
INPUT chain.
Signed-off-by: Malina Salina <malina.salina@protonmail.com>
Initial patch then modified to add unit tests and IPv6
support
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
commit 80f45e65c02bc3e4215d5037f68fdfcf56bfd49e
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: Fri Oct 18 11:40:37 2019 -0300
gitdm: add 'ibm' file
Some people from IBM does not use 'ibm.com' domain emails.
Suggested-by: Leonardo Augusto Guimarães Garcia <lagarcia@br.ibm.com>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
commit 5722e26ec586343b6edecfc243b465a9fae57ba2
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: Wed Oct 2 11:51:51 2019 +0100
util: drop logging filter/output flags
With the removal of support for log message stack traces, there is
nothing using the logging filter/output flags and they can be removed.
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
commit 9b80e0c12a75284a13e50aad2c2996ebbd8cce47
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: Wed Oct 2 11:51:51 2019 +0100
util: drop support for stack traces with logging
The log filters have supported the use of a "+" before the source match
string to request that a stack trace be emitted for every log message:
commit 548563956e484e0e43e9a66a89bdda0f95930108
Author: Daniel P. Berrange <berrange@redhat.com>
Date: Wed May 9 15:18:56 2012 +0100
Allow stack traces to be included with log messages
Sometimes it is useful to see the callpath for log messages.
This change enhances the log filter syntax so that stack traces
can be show by setting '1:+NAME' instead of '1:NAME'.
With the huge & ever increasing number of logging statements per file,
this will be incredibly verbose and have a major performance penalty.
This makes the feature impractical to use widely and as such it is not
worth the code maint cost.
Removing this seldom used feature allows us to drop the 'execinfo'
module in gnulib which provides the backtrace() function which doesn't
exist on non-Linux.
Users who want to get stack traces of parts of libvirt can use GDB,
or systemtap for live tracing with minimal perf impact.
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
commit afbdc8495e8c6322087e04b5f59d81572011b086
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: Fri Oct 18 15:43:39 2019 +0100
util: add stdlib.h include for abort() prototype
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
commit 9706476254f8fe914847554b6b52a2621fb7f5f6
Author: Michal Privoznik <mprivozn@redhat.com>
Date: Thu Oct 17 17:17:01 2019 +0200
glibcompat: Reimplement g_strdup_printf() and g_strdup_vprintf()
These functions don't really abort() on OOM. The fix was merged
upstream, but not in the minimal version we require. Provide our
own implementation which can be removed once we bump the minimal
version.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
commit b2c2a3ae91e4fefa69aeb384a9cdb24c2a43be7b
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: Fri Aug 30 13:22:54 2019 +0100
build-aux: rewrite po file minimizer in Python
As part of an goal to eliminate Perl from libvirt build tools,
rewrite the minimize-po.pl tool in Python.
This was a straight conversion, manually going line-by-line to
change the syntax from Perl to Python. Thus the overall structure
of the file and approach is the same.
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
commit 17bbdef5cb8aaa9dd8b6231824412fbd3c3ee74e
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: Fri Aug 30 13:22:54 2019 +0100
build-aux: rewrite augeas test generator in Python
As part of an goal to eliminate Perl from libvirt build tools,
rewrite the augeas-gentest.pl tool in Python.
This was a straight conversion, manually going line-by-line to
change the syntax from Perl to Python. Thus the overall structure
of the file and approach is the same.
The use of $(AUG_GENTEST) as a dependancy in the makefiles needed
to be fixed, because this was assumed to be the filename of the
script, but is in fact a full shell command line.
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
commit b36b20a1b320c81446c63fb860c3c1f7a0ea38b4
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: Fri Sep 27 14:17:54 2019 +0100
build: fix use of $(AUG_GENTEST) as a dependency
The use of $(AUG_GENTEST) as a dependency in the makefiles is
a problem because this was assumed to be the filename of the
script, but is in fact a full shell command line.
Split it into two variables, so it can be correctly used for
dependencies.
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
commit c2219efd063e2467a58aae241fc862abbf5566fc
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: Fri Oct 18 13:48:07 2019 +0100
po: refresh translations from zanata
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
commit 0ad79c1d018af2191f94c802bcf67bcd222611de
Author: Michal Privoznik <mprivozn@redhat.com>
Date: Fri Oct 18 10:07:50 2019 +0200
m4: Don't suggest attribute malloc
With glib inclusion, some of its functions have
__attribute__((__malloc__)) which make compiler realize we want
to use the same attribute for some trivial functions of ours. For
instance qemuDomainManagedSavePath(). I don't see any real
benefit into using the attribute, so disable that suggestion.
In fact, wrong use of the attribute may lead to mysterious bugs:
https://gitlab.gnome.org/GNOME/glib/issues/1465
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
ACKed-by: Peter Krempa <pkrempa@redhat.com>
commit 71519d4638e30a7c4f59a9764a7a8e5e8f679eb3
Author: Julio Faracco <jcfaracco@gmail.com>
Date: Thu Oct 17 01:30:32 2019 -0300
qemu: Generate 'xres' and 'yres' for QEMU video devices
This commit let QEMU command line define 'xres' and 'yres' properties
if XML contains both properties from video model: based on resolution
fields 'x' and 'y'. There is a conditional structure inside
qemuDomainDeviceDefValidateVideo() that validates if video model
supports this feature. This commit includes the necessary changes to
cover resolution for 'video-qxl-resolution' test cases too.
Reviewed-by: Cole Robinson <crobinso@redhat.com>
Signed-off-by: Julio Faracco <jcfaracco@gmail.com>
commit 7286279797a34b3083d85bc4556432b5e7ad9fff
Author: Julio Faracco <jcfaracco@gmail.com>
Date: Thu Oct 17 01:30:31 2019 -0300
conf: Add 'x' and 'y' resolution into video XML definition
This commit adds resolution element with parameters 'x' and 'y' into video
XML domain group definition. Both, properties were added into an element
called 'resolution' and it was added inside 'model' element. They are set
as optional. This element does not follow QEMU properties 'xres' and
'yres' format. Both HTML documentation and schema were changed too. This
commit includes a simple test case to cover resolution for QEMU video
models. The new XML format for resolution looks like:
<model ...>
<resolution x='800' y='600'/>
</model>
Reviewed-by: Cole Robinson <crobinso@redhat.com>
Signed-off-by: Julio Faracco <jcfaracco@gmail.com>
commit fbf7c23c2dfae0ff879c98130c3765b4c1ebf34e
Author: Cole Robinson <crobinso@redhat.com>
Date: Tue Oct 15 11:47:10 2019 -0400
qemu: caps: Use unique key for domCaps caching
When searching qemuCaps->domCapsCache for existing domCaps data,
we check for a matching pair of arch+virttype+machine+emulator. However
for the hash table key we only use the machine string. So if the
cache already contains:
x86_64 + kvm + pc + /usr/bin/qemu-kvm
But a new VM is defined with
x86_64 + qemu + pc + /usr/bin/qemu-kvm
We correctly fail to find matching cached domCaps, but then attempt
to use a colliding key with virHashAddEntry
Fix this by building a hash key from the 4 values, not just machine
Reviewed-by: Jonathon Jongsma <jjongsma@redhat.com>
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Signed-off-by: Cole Robinson <crobinso@redhat.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-10-20 4:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-20 4:00 [Xen-devel] [libvirt test] 142904: regressions - FAIL 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.