New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-build » libvirt-centos-7 #139

Thursday, 26 October 2023


https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-cento...:

[berrange] Set release date for 2.5.0

[berrange] Post release version bump to 3.0.0

[jferlan] Add blkdeviotune group_name parameter

------------------------------------------
Started by upstream project "libvirt-perl-master-build" build number 138
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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
 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
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-centos-7 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-cento...
...
 git rev-parse --is-inside-work-tree # timeout=10 Fetching
changes from the remote Git repository
...
 git config remote.origin.url
git://n64.pufty.ci.centos.org/libvirt-perl.git # timeout=10 Fetching upstream
changes from git://n64.pufty.ci.centos.org/libvirt-perl.git
...
 git --version # timeout=10
 git -c core.askpass=true fetch --tags --progress
git://n64.pufty.ci.centos.org/libvirt-perl.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision a305f60eaa09576a6dd10b14a83ce719646f7bc9
(refs/remotes/origin/master)
...
 git config core.sparsecheckout # timeout=10
 git checkout -f a305f60eaa09576a6dd10b14a83ce719646f7bc9
 git rev-list 8403193bf1f1417e8e9ae59c60be79d3b3a0db13 # timeout=10 Cleaning
workspace
...
 git rev-parse --verify HEAD # timeout=10 Resetting working
tree
...
 git reset --hard # timeout=10
 git clean -fdx # timeout=10 [libvirt-centos-7] $ /bin/sh -xe
/tmp/hudson6874340661463717798.sh
+ perl Makefile.PL PREFIX=/home/jenkins/build/libvirt
libvirt >= 3.0.0 is required
Build step 'Execute shell' marked build as failure

2024

2023

2022

2021

2020

2019

2018

2017

2016

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-build » libvirt-centos-7 #138