[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-build » libvirt-fedora-24 #138
26 Oct
2023
26 Oct
'23
11:13 a.m.
https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-fedora-24/138/Changes: [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-fedora-24 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-fedora-24/ws/> > 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-fedora-24] $ /bin/sh -xe /tmp/hudson8589944703721762841.sh + perl Makefile.PL PREFIX=/home/jenkins/build/libvirt libvirt >= 3.0.0 is required Build step 'Execute shell' marked build as failure
26 Oct
26 Oct
11:13 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-build » libvirt-fedora-24 #139
https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-fedora-24/139/------------------------------------------ Started by upstream project "libvirt-perl-master-build" build number 139 originally caused by: Started by upstream project "libvirt-master-build" build number 201 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-24 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-fedora-24/ws/> > 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 a305f60eaa09576a6dd10b14a83ce719646f7bc9 # 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-fedora-24] $ /bin/sh -xe /tmp/hudson1857625996930702402.sh + perl Makefile.PL PREFIX=/home/jenkins/build/libvirt libvirt >= 3.0.0 is required Build step 'Execute shell' marked build as failure
11:13 a.m.
New subject: [Libvirt-ci] Jenkins build is back to normal : libvirt-perl-master-build » libvirt-fedora-24 #140
831
Age (days ago)
831
Last active (days ago)
2 comments
1 participants
participants (1)
-
ci@centos.org