April 2020 - CI - libvirt List Archives

Still Failing: libvirt/libvirt#3352 (master - 7e5a40f)
by Travis CI 23 Apr '20

23 Apr '20

Build Update for libvirt/libvirt ------------------------------------- Build: #3352 Status: Still Failing Duration: 19 mins and 51 secs Commit: 7e5a40f (master) Author: Julio Faracco Message: tests: Add tests for <lease/> to cover dnsmasq settings New tests are required to cover some new XML syntax entry for <lease/> option. This includes schema testing and other features like unit attribute and lease value. This commit includes hostsfile checks adding new files for each test case that is manipulating <host/> tag. Signed-off-by: Julio Faracco <jcfaracco(a)gmail.com> Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Reviewed-by: Michal Privoznik <mprivozn(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/5670fb579407...7e5a40fd0f58 View the full build log and details: https://travis-ci.org/github/libvirt/libvirt/builds/678513976?utm_medium=no… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

Still Failing: libvirt/libvirt#3351 (master - 5670fb5)
by Travis CI 22 Apr '20

22 Apr '20

Build Update for libvirt/libvirt ------------------------------------- Build: #3351 Status: Still Failing Duration: 27 mins and 28 secs Commit: 5670fb5 (master) Author: Chen Hanxiao Message: docs: drvqemu: trivial fix for qemu commands passthrough element <qemu:commandline> should be the child of <domain> Signed-off-by: Chen Hanxiao <chen_han_xiao(a)126.com> Reviewed-by: Ján Tomko <jtomko(a)redhat.com> Signed-off-by: Ján Tomko <jtomko(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/468c9811309d...5670fb579407 View the full build log and details: https://travis-ci.org/github/libvirt/libvirt/builds/678258265?utm_medium=no… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

Still Failing: libvirt/libvirt#3350 (master - 468c981)
by Travis CI 22 Apr '20

22 Apr '20

Build Update for libvirt/libvirt ------------------------------------- Build: #3350 Status: Still Failing Duration: 18 mins and 56 secs Commit: 468c981 (master) Author: Jim Fehlig Message: news: Document new Xen hypervisor features Signed-off-by: Jim Fehlig <jfehlig(a)suse.com> Reviewed-by: Andrea Bolognani <abologna(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/9a13704818e4...468c9811309d View the full build log and details: https://travis-ci.org/github/libvirt/libvirt/builds/678252270?utm_medium=no… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

Still Failing: libvirt/libvirt#3349 (master - 9a13704)
by Travis CI 22 Apr '20

22 Apr '20

Build Update for libvirt/libvirt ------------------------------------- Build: #3349 Status: Still Failing Duration: 18 mins and 51 secs Commit: 9a13704 (master) Author: Michal Privoznik Message: udevHandleOneDevice: Remove old instance of device on "move" When a device is "move"-d (this basically means it was renamed), we add the new device onto our list but keep the old there too. Fortunately, udev sets this DEVPATH_OLD property which points to the old device path. We can use it to remove the old instance. To test this try renaming an interface, for instance: # ip link set tunl0 name tunl1 # ip link set tunl1 name tunl0 One problem with udev is that it sends old ifname in INTERFACE property, which creates a problem for us, the property is where we get the ifname from and use it then to query all kind of info about the interface. Well, if it is non-existent then we can't query anything. This happens if ifname rename is suppressed (net.ifnames=0 on kernel cmd line for instance). Fortunately, we can use "kernel" source for udev events which has always the fresh info. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Reviewed-by: Martin Kletzander <mkletzan(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/c740ae69c382...9a13704818e4 View the full build log and details: https://travis-ci.org/github/libvirt/libvirt/builds/678109815?utm_medium=no… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

Build failed in Jenkins: libvirt-go-xml-check » libvirt-centos-7 #1171
by ci＠centos.org 22 Apr '20

22 Apr '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-centos-7/117…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 1171 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 1175 originally caused by: Started by upstream project "libvirt-build" build number 1362 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-centos-7 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-centos-7/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins4075374055874646023.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (47.61s) xml_test.go:374: testdata/libvirt/tests/xlconfigdata/test-fullvirt-hypervisor-features.xml: /domain[0]/features[0]/xen[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-centos-7/ws/> 47.692s Build step 'Execute shell' marked build as failure

1 6

Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-31 #1171
by ci＠centos.org 22 Apr '20

22 Apr '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-31/11…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 1171 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 1175 originally caused by: Started by upstream project "libvirt-build" build number 1362 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-31 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-31/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins4390146426879067792.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (40.49s) xml_test.go:374: testdata/libvirt/tests/xlconfigdata/test-fullvirt-hypervisor-features.xml: /domain[0]/features[0]/xen[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-31/ws/> 40.645s Build step 'Execute shell' marked build as failure

1 6

Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-30 #1171
by ci＠centos.org 22 Apr '20

22 Apr '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-30/11…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 1171 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 1175 originally caused by: Started by upstream project "libvirt-build" build number 1362 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-30 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-30/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins389712914236609031.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (61.43s) xml_test.go:374: testdata/libvirt/tests/xlconfigdata/test-fullvirt-hypervisor-features.xml: /domain[0]/features[0]/xen[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-30/ws/> 61.570s Build step 'Execute shell' marked build as failure

1 6

Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-rawhide #1171
by ci＠centos.org 22 Apr '20

22 Apr '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-rawhi…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 1171 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 1175 originally caused by: Started by upstream project "libvirt-build" build number 1362 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-rawhide (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-rawhi…> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins17980261972937434133.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (72.43s) xml_test.go:374: testdata/libvirt/tests/xlconfigdata/test-fullvirt-hypervisor-features.xml: /domain[0]/features[0]/xen[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-rawhi…> 72.687s Build step 'Execute shell' marked build as failure

1 6

Build failed in Jenkins: libvirt-go-xml-check » libvirt-freebsd-12 #1171
by ci＠centos.org 22 Apr '20

22 Apr '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-12/1…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 1171 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 1175 originally caused by: Started by upstream project "libvirt-build" build number 1362 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-freebsd-12 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-12/w…> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins15397110455996798484.sh + export 'TEST_ARGS=-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (40.70s) xml_test.go:374: testdata/libvirt/tests/xlconfigdata/test-fullvirt-hypervisor-features.xml: /domain[0]/features[0]/xen[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _/usr<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-12/w…> 40.780s Build step 'Execute shell' marked build as failure

1 6

Build failed in Jenkins: libvirt-go-xml-check » libvirt-freebsd-11 #1171
by ci＠centos.org 22 Apr '20

22 Apr '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-11/1…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 1171 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 1175 originally caused by: Started by upstream project "libvirt-build" build number 1362 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-freebsd-11 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-11/w…> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins16020591609928945236.sh + export 'TEST_ARGS=-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (38.42s) xml_test.go:374: testdata/libvirt/tests/xlconfigdata/test-fullvirt-hypervisor-features.xml: /domain[0]/features[0]/xen[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _/usr<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-11/w…> 38.571s Build step 'Execute shell' marked build as failure

1 6