- CI - libvirt List Archives

[Libvirt-ci] Jenkins build is back to normal : libvirt-check » libvirt-debian-9 #803
by ci＠centos.org 28 Nov '19

28 Nov '19

See <https://ci.centos.org/job/libvirt-check/systems=libvirt-debian-9/803/displa…>

1 0

[Libvirt-ci] Jenkins build is back to normal : libvirt-check » libvirt-centos-7 #803
by ci＠centos.org 28 Nov '19

28 Nov '19

See <https://ci.centos.org/job/libvirt-check/systems=libvirt-centos-7/803/displa…>

1 0

[Libvirt-ci] Build failed in Jenkins: libosinfo-build » libvirt-fedora-rawhide #271
by ci＠centos.org 28 Nov '19

28 Nov '19

See <https://ci.centos.org/job/libosinfo-build/systems=libvirt-fedora-rawhide/27…> Changes: [fidencio] device-driver: Add "priority" attribute [fidencio] os: Add "get_device_drivers_prioritized" ------------------------------------------ Started by upstream project "libosinfo-build" build number 271 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change 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/libosinfo-build/systems=libvirt-fedora-rawhide/ws/> No credentials specified Cloning the remote Git repository Cloning repository https://gitlab.com/libosinfo/libosinfo.git > git init <https://ci.centos.org/job/libosinfo-build/systems=libvirt-fedora-rawhide/ws/> # timeout=10 Fetching upstream changes from https://gitlab.com/libosinfo/libosinfo.git > git --version # timeout=10 > git fetch --tags --progress https://gitlab.com/libosinfo/libosinfo.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://gitlab.com/libosinfo/libosinfo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://gitlab.com/libosinfo/libosinfo.git # timeout=10 Fetching upstream changes from https://gitlab.com/libosinfo/libosinfo.git > git fetch --tags --progress https://gitlab.com/libosinfo/libosinfo.git +refs/heads/*:refs/remotes/origin/* Checking out Revision afffabae21a99efa42047cd65c5cdfa05babc259 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f afffabae21a99efa42047cd65c5cdfa05babc259 Commit message: "os: Add "get_device_drivers_prioritized"" > git rev-list --no-walk 5011123a6159e7293dc8a64159268c9abf96939f # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 [libosinfo] $ /bin/sh -xe /tmp/jenkins1467834337233549361.sh + rm -rf build + mkdir build + cd build + meson .. . --prefix=/home/jenkins/build/libvirt /tmp/jenkins1467834337233549361.sh: line 6: meson: command not found Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: libosinfo-build » libvirt-freebsd-11 #271
by ci＠centos.org 28 Nov '19

28 Nov '19

See <https://ci.centos.org/job/libosinfo-build/systems=libvirt-freebsd-11/271/di…> Changes: [fidencio] device-driver: Add "priority" attribute [fidencio] os: Add "get_device_drivers_prioritized" ------------------------------------------ Started by upstream project "libosinfo-build" build number 271 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change 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/libosinfo-build/systems=libvirt-freebsd-11/ws/> No credentials specified Cloning the remote Git repository Cloning repository https://gitlab.com/libosinfo/libosinfo.git > git init <https://ci.centos.org/job/libosinfo-build/systems=libvirt-freebsd-11/ws/> # timeout=10 Fetching upstream changes from https://gitlab.com/libosinfo/libosinfo.git > git --version # timeout=10 > git fetch --tags --progress https://gitlab.com/libosinfo/libosinfo.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://gitlab.com/libosinfo/libosinfo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://gitlab.com/libosinfo/libosinfo.git # timeout=10 Fetching upstream changes from https://gitlab.com/libosinfo/libosinfo.git > git fetch --tags --progress https://gitlab.com/libosinfo/libosinfo.git +refs/heads/*:refs/remotes/origin/* Checking out Revision afffabae21a99efa42047cd65c5cdfa05babc259 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f afffabae21a99efa42047cd65c5cdfa05babc259 Commit message: "os: Add "get_device_drivers_prioritized"" > git rev-list --no-walk 5011123a6159e7293dc8a64159268c9abf96939f # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 [libosinfo] $ /bin/sh -xe /tmp/jenkins4434238580308385610.sh + rm -rf build + mkdir build + cd build + meson .. . '--prefix=/home/jenkins/build/libvirt' /tmp/jenkins4434238580308385610.sh: meson: not found Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: libosinfo-build » libvirt-debian-9 #271
by ci＠centos.org 28 Nov '19

28 Nov '19

See <https://ci.centos.org/job/libosinfo-build/systems=libvirt-debian-9/271/disp…> Changes: [fidencio] device-driver: Add "priority" attribute [fidencio] os: Add "get_device_drivers_prioritized" ------------------------------------------ Started by upstream project "libosinfo-build" build number 271 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libosinfo-build/systems=libvirt-debian-9/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://gitlab.com/libosinfo/libosinfo.git # timeout=10 Fetching upstream changes from https://gitlab.com/libosinfo/libosinfo.git > git --version # timeout=10 > git fetch --tags --progress https://gitlab.com/libosinfo/libosinfo.git +refs/heads/*:refs/remotes/origin/* Checking out Revision afffabae21a99efa42047cd65c5cdfa05babc259 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f afffabae21a99efa42047cd65c5cdfa05babc259 Commit message: "os: Add "get_device_drivers_prioritized"" > git rev-list --no-walk 5011123a6159e7293dc8a64159268c9abf96939f # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 [libosinfo] $ /bin/sh -xe /tmp/jenkins277675047841104966.sh + rm -rf build + mkdir build + cd build + meson .. . --prefix=/home/jenkins/build/libvirt /tmp/jenkins277675047841104966.sh: 6: /tmp/jenkins277675047841104966.sh: meson: not found Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: libosinfo-build » libvirt-centos-7 #271
by ci＠centos.org 28 Nov '19

28 Nov '19

See <https://ci.centos.org/job/libosinfo-build/systems=libvirt-centos-7/271/disp…> Changes: [fidencio] device-driver: Add "priority" attribute [fidencio] os: Add "get_device_drivers_prioritized" ------------------------------------------ Started by upstream project "libosinfo-build" build number 271 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change 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/libosinfo-build/systems=libvirt-centos-7/ws/> No credentials specified Cloning the remote Git repository Cloning repository https://gitlab.com/libosinfo/libosinfo.git > git init <https://ci.centos.org/job/libosinfo-build/systems=libvirt-centos-7/ws/> # timeout=10 Fetching upstream changes from https://gitlab.com/libosinfo/libosinfo.git > git --version # timeout=10 > git fetch --tags --progress https://gitlab.com/libosinfo/libosinfo.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://gitlab.com/libosinfo/libosinfo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://gitlab.com/libosinfo/libosinfo.git # timeout=10 Fetching upstream changes from https://gitlab.com/libosinfo/libosinfo.git > git fetch --tags --progress https://gitlab.com/libosinfo/libosinfo.git +refs/heads/*:refs/remotes/origin/* Checking out Revision afffabae21a99efa42047cd65c5cdfa05babc259 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f afffabae21a99efa42047cd65c5cdfa05babc259 Commit message: "os: Add "get_device_drivers_prioritized"" > git rev-list --no-walk 5011123a6159e7293dc8a64159268c9abf96939f # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 [libosinfo] $ /bin/sh -xe /tmp/jenkins8854951521072142696.sh + rm -rf build + mkdir build + cd build + meson .. . --prefix=/home/jenkins/build/libvirt /tmp/jenkins8854951521072142696.sh: line 6: meson: command not found Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Still Failing: libvirt/libvirt#2892 (master - 83254ea)
by Travis CI 28 Nov '19

28 Nov '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2892 Status: Still Failing Duration: 38 mins and 11 secs Commit: 83254ea (master) Author: Michal Privoznik Message: news: Update for 5.10.0 release Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Reviewed-by: Ján Tomko <jtomko(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/d310b0869753...83254ea750b4 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617797081?utm_medium=notificat… -- 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

[Libvirt-ci] Still Failing: libvirt/libvirt#2891 (master - d310b08)
by Travis CI 28 Nov '19

28 Nov '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2891 Status: Still Failing Duration: 40 mins and 1 sec Commit: d310b08 (master) Author: Peter Krempa Message: qemu: blockjob: Finish handling job with broken data Now that we have a separate job type which will not trigger normal code paths for terminating job we can remove the ad-hoc handling. This possibly fixes the issue of a broken job inheriting the disk and then finishing in which case we'd not detach the backing chain. Signed-off-by: Peter Krempa <pkrempa(a)redhat.com> Reviewed-by: Cole Robinson <crobinso(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/27660f7990f2...d310b0869753 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617770658?utm_medium=notificat… -- 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

[Libvirt-ci] Still Failing: libvirt/libvirt#2890 (master - 27660f7)
by Travis CI 28 Nov '19

28 Nov '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2890 Status: Still Failing Duration: 38 mins and 40 secs Commit: 27660f7 (master) Author: Daniel P. Berrangé Message: util: whitelist Oracle ACFS as a shared filesystem The magic number is taken from the coreutils stat.c file since there is no constant for it in normal system headers. Reviewed-by: Daniel Henrique Barboza <danielhb413(a)gmail.com> Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/a10eb613404f...27660f7990f2 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617749660?utm_medium=notificat… -- 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

[Libvirt-ci] Still Failing: libvirt/libvirt#2889 (master - a10eb61)
by Travis CI 28 Nov '19

28 Nov '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2889 Status: Still Failing Duration: 39 mins and 13 secs Commit: a10eb61 (master) Author: Peter Krempa Message: Revert "qemu: Don't repeat virDomainObjEndAPI in qemuDomainBlockPull" This reverts commit 421c9550f5446729b513ee50f5c44e6f6969b5a2 qemuDomainBlockPullCommon calls virDomainObjEndAPI internally so the original commit made us shed two references of @vm instead of one getting us into a premature free of @vm. This is not a straight revert as qemuDomainBlockPull was modified meanwhile. I've also added a warning comment that @vm is consumed. https://bugzilla.redhat.com/show_bug.cgi?id=1777230 Signed-off-by: Peter Krempa <pkrempa(a)redhat.com> Reviewed-by: Ján Tomko <jtomko(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/c8579871a980...a10eb613404f View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617724609?utm_medium=notificat… -- 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