libvirt List Archives
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

CI

Thread Start a new thread
Download
Threads by month
  • ----- 2025 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2020 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2019 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2018 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2017 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2016 -----
  • December
  • November
  • October
  • September
  • August
  • July
ci@lists.libvirt.org

October 2023

  • 2 participants
  • 746 discussions
[Libvirt-ci] Build failed in Jenkins: virt-manager-master-check » libvirt-centos-7 #155
by ci@centos.org 27 Oct '23

27 Oct '23
https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-centos-… Started by upstream project "virt-manager-master-check" build number 155 originally caused by: Started by upstream project "virt-manager-master-build" build number 156 originally caused by: Started by upstream project "libvirt-python-master-build" build number 131 originally caused by: Started by upstream project "libvirt-master-build" build number 204 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-centos-7 (libvirt) in workspace <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-centos-…> [libvirt-centos-7] $ /bin/sh -xe /tmp/hudson5018082928255651884.sh + python setup.py test running test .......................................................................................................................................................................................................................................................................................................................................................................................................................... ---------------------------------------------------------------------- Ran 410 tests in 239.902s OK /tmp/hudson5018082928255651884.sh: line 2: 26327 Segmentation fault (core dumped) python setup.py test Build step 'Execute shell' marked build as failure
1 1
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-master-build » libvirt-freebsd #205
by ci@centos.org 27 Oct '23

27 Oct '23
https://ci.centos.org/job/libvirt-master-build/systems=libvirt-freebsd/205/…: [mprivozn] libvirt.spec: Package libnss_libvirt_guest.so.2 [mkletzan] conf: Make scheduler formatting simpler [mprivozn] virDomainObjGetShortName: take virDomainDef [mprivozn] qemu: Create hugepage path on per domain basis [mprivozn] security: Drop virSecurityManagerSetHugepages [cbosdonnat] lxc: monitor now holds a reference to the domain [pkrempa] qemu: Don't try to find compression program for "raw" memory images ------------------------------------------ [...truncated 3979 lines...] GEN test_virtlogd.aug CC util/libvirt_util_la-viralloc.lo CC util/libvirt_util_la-virarch.lo CC util/libvirt_util_la-viratomic.lo CC util/libvirt_util_la-viraudit.lo CC util/libvirt_util_la-virauth.lo CC util/libvirt_util_la-virauthconfig.lo CC util/libvirt_util_la-virbuffer.lo CC util/libvirt_util_la-virbitmap.lo CC util/libvirt_util_la-virperf.lo CC util/libvirt_util_la-vircgroup.lo CC util/libvirt_util_la-virclosecallbacks.lo CC util/libvirt_util_la-vircommand.lo CC util/libvirt_util_la-virconf.lo CC util/libvirt_util_la-vircrypto.lo CC util/libvirt_util_la-virdbus.lo CC util/libvirt_util_la-virdnsmasq.lo CC util/libvirt_util_la-virebtables.lo CC util/libvirt_util_la-virerror.lo CC util/libvirt_util_la-virevent.lo CC util/libvirt_util_la-vireventpoll.lo CC util/libvirt_util_la-virfile.lo CC util/libvirt_util_la-virfirewall.lo CC util/libvirt_util_la-virfirmware.lo CC util/libvirt_util_la-virgettext.lo CC util/libvirt_util_la-virgic.lo CC util/libvirt_util_la-virhash.lo CC util/libvirt_util_la-virhashcode.lo CC util/libvirt_util_la-virhook.lo CC util/libvirt_util_la-virhostcpu.lo CC util/libvirt_util_la-virhostdev.lo CC util/libvirt_util_la-virhostmem.lo CC util/libvirt_util_la-viridentity.lo CC util/libvirt_util_la-virinitctl.lo CC util/libvirt_util_la-viriptables.lo CC util/libvirt_util_la-viriscsi.lo CC util/libvirt_util_la-virjson.lo CC util/libvirt_util_la-virkeycode.lo CC util/libvirt_util_la-virkeyfile.lo CC util/libvirt_util_la-virlease.lo CC util/libvirt_util_la-virlockspace.lo CC util/libvirt_util_la-virlog.lo CC util/libvirt_util_la-virmacaddr.lo CC util/libvirt_util_la-virmacmap.lo CC util/libvirt_util_la-virnetdev.lo CC util/libvirt_util_la-virnetdevbandwidth.lo CC util/libvirt_util_la-virnetdevbridge.lo CC util/libvirt_util_la-virnetdevip.lo CC util/libvirt_util_la-virnetdevmacvlan.lo CC util/libvirt_util_la-virnetdevmidonet.lo CC util/libvirt_util_la-virnetdevopenvswitch.lo CC util/libvirt_util_la-virnetdevtap.lo CC util/libvirt_util_la-virnetdevveth.lo CC util/libvirt_util_la-virnetdevvlan.lo CC util/libvirt_util_la-virnetdevvportprofile.lo CC util/libvirt_util_la-virnetlink.lo CC util/libvirt_util_la-virnodesuspend.lo CC util/libvirt_util_la-virkmod.lo CC util/libvirt_util_la-virnuma.lo CC util/libvirt_util_la-virobject.lo CC util/libvirt_util_la-virpci.lo CC util/libvirt_util_la-virpidfile.lo CC util/libvirt_util_la-virpolkit.lo CC util/libvirt_util_la-virportallocator.lo CC util/libvirt_util_la-virprocess.lo CC util/libvirt_util_la-virqemu.lo CC util/libvirt_util_la-virrandom.lo CC util/libvirt_util_la-virrotatingfile.lo CC util/libvirt_util_la-virscsi.lo CC util/libvirt_util_la-virscsivhost.lo CC util/libvirt_util_la-virseclabel.lo CC util/libvirt_util_la-virsecret.lo CC util/libvirt_util_la-virsexpr.lo CC util/libvirt_util_la-virsocketaddr.lo CC util/libvirt_util_la-virstats.lo CC util/libvirt_util_la-virstorageencryption.lo CC util/libvirt_util_la-virstoragefile.lo CC util/libvirt_util_la-virstring.lo CC util/libvirt_util_la-virsysinfo.lo CC util/libvirt_util_la-virsystemd.lo CC util/libvirt_util_la-virthread.lo CC util/libvirt_util_la-virthreadjob.lo CC util/libvirt_util_la-virthreadpool.lo CC util/libvirt_util_la-virtime.lo CC util/libvirt_util_la-virtpm.lo CC util/libvirt_util_la-virtypedparam.lo CC util/libvirt_util_la-virusb.lo CC util/libvirt_util_la-viruri.lo CC util/libvirt_util_la-virutil.lo CC util/libvirt_util_la-viruuid.lo CC util/libvirt_util_la-virxml.lo CC conf/libvirt_conf_la-netdev_bandwidth_conf.lo CC conf/libvirt_conf_la-netdev_vport_profile_conf.lo CC conf/libvirt_conf_la-netdev_vlan_conf.lo CC conf/libvirt_conf_la-capabilities.lo CC conf/libvirt_conf_la-domain_addr.lo CC conf/libvirt_conf_la-domain_capabilities.lo CC conf/libvirt_conf_la-domain_conf.lo CC conf/libvirt_conf_la-domain_audit.lo CC conf/libvirt_conf_la-domain_nwfilter.lo CC conf/libvirt_conf_la-snapshot_conf.lo CC conf/libvirt_conf_la-numa_conf.lo CC conf/libvirt_conf_la-virdomainobjlist.lo CC conf/libvirt_conf_la-object_event.lo CC conf/libvirt_conf_la-domain_event.lo CC conf/libvirt_conf_la-network_event.lo CC conf/libvirt_conf_la-storage_event.lo CC conf/libvirt_conf_la-node_device_event.lo CC conf/libvirt_conf_la-network_conf.lo CC conf/libvirt_conf_la-networkcommon_conf.lo CC conf/libvirt_conf_la-nwfilter_params.lo CC conf/libvirt_conf_la-nwfilter_ipaddrmap.lo CC conf/libvirt_conf_la-nwfilter_conf.lo CC conf/libvirt_conf_la-node_device_conf.lo CC conf/libvirt_conf_la-storage_conf.lo CC conf/libvirt_conf_la-interface_conf.lo CC conf/libvirt_conf_la-secret_conf.lo CC conf/libvirt_conf_la-virsecretobj.lo CC conf/libvirt_conf_la-cpu_conf.lo CC conf/libvirt_conf_la-virchrdev.lo CC conf/libvirt_conf_la-device_conf.lo CC cpu/libvirt_cpu_la-cpu.lo CC cpu/libvirt_cpu_la-cpu_x86.lo CC cpu/libvirt_cpu_la-cpu_s390.lo CC cpu/libvirt_cpu_la-cpu_arm.lo CC cpu/libvirt_cpu_la-cpu_ppc64.lo CC cpu/libvirt_cpu_la-cpu_map.lo CC secret/libvirt_secret_la-secret_util.lo CC vmx/libvirt_vmx_la-vmx.lo CC locking/libvirt_driver_la-lock_manager.lo CC locking/libvirt_driver_la-lock_driver_nop.lo CC locking/libvirt_driver_la-domain_lock.lo CC logging/libvirt_driver_la-log_manager.lo CC logging/libvirt_driver_la-log_protocol.lo CC test/libvirt_driver_test_la-test_driver.lo CC remote/libvirt_driver_remote_la-remote_driver.lo CC remote/libvirt_driver_remote_la-remote_protocol.lo CC remote/libvirt_driver_remote_la-lxc_protocol.lo CC remote/libvirt_driver_remote_la-qemu_protocol.lo CC rpc/libvirt_net_rpc_client_la-virnetclientprogram.lo CC rpc/libvirt_net_rpc_client_la-virnetclientstream.lo CC rpc/libvirt_net_rpc_client_la-virnetclient.lo CC rpc/libvirt_net_rpc_server_la-virnetserverprogram.lo CC rpc/libvirt_net_rpc_server_la-virnetserverservice.lo CC rpc/libvirt_net_rpc_server_la-virnetserverclient.lo CC rpc/libvirt_net_rpc_server_la-virnetservermdns.lo CC rpc/libvirt_net_rpc_server_la-virnetdaemon.lo CC rpc/libvirt_net_rpc_server_la-virnetserver.lo CC rpc/libvirt_net_rpc_la-virnetmessage.lo CC rpc/libvirt_net_rpc_la-virnetsocket.lo CC rpc/libvirt_net_rpc_la-virkeepalive.lo CC rpc/libvirt_net_rpc_la-virnetprotocol.lo CC rpc/libvirt_net_rpc_la-virkeepaliveprotocol.lo CC rpc/libvirt_net_rpc_la-virnetsshsession.lo CC rpc/libvirt_net_rpc_la-virnettlscontext.lo CC phyp/libvirt_driver_phyp_la-phyp_driver.lo CC vmware/libvirt_driver_vmware_la-vmware_driver.lo CC vmware/libvirt_driver_vmware_la-vmware_conf.lo CC esx/libvirt_driver_esx_la-esx_driver.lo CC esx/libvirt_driver_esx_la-esx_interface_driver.lo CC esx/libvirt_driver_esx_la-esx_network_driver.lo CC esx/libvirt_driver_esx_la-esx_storage_driver.lo CC esx/libvirt_driver_esx_la-esx_storage_backend_vmfs.lo CC esx/libvirt_driver_esx_la-esx_storage_backend_iscsi.lo CC esx/libvirt_driver_esx_la-esx_stream.lo CC esx/libvirt_driver_esx_la-esx_util.lo CC esx/libvirt_driver_esx_la-esx_vi.lo CC esx/libvirt_driver_esx_la-esx_vi_methods.lo CC esx/libvirt_driver_esx_la-esx_vi_types.lo CC security/libvirt_security_manager_la-security_driver.lo CC security/libvirt_security_manager_la-security_nop.lo CC security/libvirt_security_manager_la-security_stack.lo CC security/libvirt_security_manager_la-security_dac.lo CC security/libvirt_security_manager_la-security_manager.lo CC access/libvirt_driver_access_la-viraccessperm.lo CC access/libvirt_driver_access_la-viraccessmanager.lo CC access/libvirt_driver_access_la-viraccessdrivernop.lo CC access/libvirt_driver_access_la-viraccessdriverstack.lo CC access/libvirt_driver_access_la-viraccessapicheck.lo CC access/libvirt_driver_access_la-viraccessapicheckqemu.lo CC access/libvirt_driver_access_la-viraccessapichecklxc.lo CC admin/libvirt_admin_la-admin_protocol.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_glue.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_driver.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_snapshot_conf.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V2_2.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V3_0.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V3_1.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V3_2.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V4_0.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V4_1.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V4_2.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V4_2_20.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V4_3.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V4_3_4.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V5_0.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_V5_1.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_common.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_network.lo CC vbox/libvirt_driver_vbox_impl_la-vbox_storage.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_agent.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_alias.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_blockjob.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_capabilities.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_command.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_parse_command.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_domain.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_domain_address.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_cgroup.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_hostdev.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_hotplug.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_conf.lo CC qemu/libvirt_driver_qemu_impl_la-qemu_process.lo ../../src/qemu/qemu_conf.c:1478:9: error: variable 'ret' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes-uninitialized] if (base && domPath) ^~~~~~~~~~~~~~~ ../../src/qemu/qemu_conf.c:1482:12: note: uninitialized use occurs here return ret; ^~~ ../../src/qemu/qemu_conf.c:1478:5: note: remove the 'if' if its condition is always true if (base && domPath) ^~~~~~~~~~~~~~~~~~~~ ../../src/qemu/qemu_conf.c:1478:9: error: variable 'ret' is used uninitialized whenever '&&' condition is false [-Werror,-Wsometimes-uninitialized] if (base && domPath) ^~~~ ../../src/qemu/qemu_conf.c:1482:12: note: uninitialized use occurs here return ret; ^~~ ../../src/qemu/qemu_conf.c:1478:9: note: remove the '&&' if its condition is always true if (base && domPath) ^~~~~~~ ../../src/qemu/qemu_conf.c:1476:14: note: initialize the variable 'ret' to silence this warning char *ret; ^ = NULL 2 errors generated. Makefile:9088: recipe for target 'qemu/libvirt_driver_qemu_impl_la-qemu_conf.lo' failed gmake[3]: *** [qemu/libvirt_driver_qemu_impl_la-qemu_conf.lo] Error 1 gmake[3]: *** Waiting for unfinished jobs.... gmake[3]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-master-build/systems=libvirt-freebsd/ws/b…'> Makefile:5443: recipe for target 'all' failed gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-master-build/systems=libvirt-freebsd/ws/b…'> Makefile:2013: recipe for target 'all-recursive' failed gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-master-build/systems=libvirt-freebsd/ws/b…'> Makefile:1910: recipe for target 'all' failed gmake: *** [all] Error 2 Build step 'Execute shell' marked build as failure
1 3
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-test » libvirt-fedora-24 #124
by ci@centos.org 27 Oct '23

27 Oct '23
https://ci.centos.org/job/libvirt-perl-master-test/systems=libvirt-fedora-2… [...truncated 960 lines...] Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started 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-test/systems=libvirt-fedora-2…> [libvirt-fedora-24] $ /bin/sh -xe /tmp/hudson8168039613706359305.sh + make -j3 test TEST_MAINTAINER=1 PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/005-pod.t ............ ok # Failed test 'Pod coverage on Sys::Virt::Domain' # at /usr/share/perl5/vendor_perl/Test/Pod/Coverage.pm line 133. # Coverage for Sys::Virt::Domain is 99.9%, with 1 naked subroutine: # TUNABLE_BLKDEV_GROUP_NAME # Looks like you failed 1 test of 13. t/010-pod-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/13 subtests t/015-changes.t ........ ok t/020-constants.t ...... ok # Failed test 'VIR_PERF_PARAM_BRANCH_INSTRUCTIONS' # at t/030-api-coverage.t line 209. # Looks like you failed 1 test of 1526. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1526 subtests t/100-connect.t ........ ok t/200-domains.t ........ ok t/300-networks.t ....... ok t/400-storage-pools.t .. ok t/500-storage-vols.t ... ok t/600-interfaces.t ..... ok t/800-events.t ......... ok Test Summary Report ------------------- t/010-pod-coverage.t (Wstat: 256 Tests: 13 Failed: 1) Failed test: 2 Non-zero exit status: 1 t/030-api-coverage.t (Wstat: 256 Tests: 1526 Failed: 1) Failed test: 1507 Non-zero exit status: 1 Files=12, Tests=1778, 12 wallclock secs ( 0.39 usr 0.05 sys + 5.84 cusr 0.36 csys = 6.64 CPU) Result: FAIL Failed 2/12 test programs. 2/1778 subtests failed. Makefile:1030: recipe for target 'test_dynamic' failed make: *** [test_dynamic] Error 255 Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-test » libvirt-fedora-rawhide #124
by ci@centos.org 27 Oct '23

27 Oct '23
https://ci.centos.org/job/libvirt-perl-master-test/systems=libvirt-fedora-r… [...truncated 960 lines...] Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started 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-rawhide (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-master-test/systems=libvirt-fedora-r…> [libvirt-fedora-rawhide] $ /bin/sh -xe /tmp/hudson202375066115461311.sh + make -j3 test TEST_MAINTAINER=1 "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Virt.bs blib/arch/auto/Sys/Virt/Virt.bs 644 PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/005-pod.t ............ ok # Failed test 'Pod coverage on Sys::Virt::Domain' # at /usr/share/perl5/vendor_perl/Test/Pod/Coverage.pm line 133. # Coverage for Sys::Virt::Domain is 99.9%, with 1 naked subroutine: # TUNABLE_BLKDEV_GROUP_NAME # Looks like you failed 1 test of 13. t/010-pod-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/13 subtests t/015-changes.t ........ ok t/020-constants.t ...... ok # Failed test 'VIR_PERF_PARAM_BRANCH_INSTRUCTIONS' # at t/030-api-coverage.t line 209. # Looks like you failed 1 test of 1526. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1526 subtests t/100-connect.t ........ ok t/200-domains.t ........ ok t/300-networks.t ....... ok t/400-storage-pools.t .. ok t/500-storage-vols.t ... ok t/600-interfaces.t ..... ok t/800-events.t ......... ok Test Summary Report ------------------- t/010-pod-coverage.t (Wstat: 256 Tests: 13 Failed: 1) Failed test: 11 Non-zero exit status: 1 t/030-api-coverage.t (Wstat: 256 Tests: 1526 Failed: 1) Failed test: 1507 Non-zero exit status: 1 Files=12, Tests=1778, 18 wallclock secs ( 0.41 usr 0.14 sys + 5.93 cusr 1.39 csys = 7.87 CPU) Result: FAIL Failed 2/12 test programs. 2/1778 subtests failed. make: *** [Makefile:1018: test_dynamic] Error 255 Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-test » libvirt-fedora-23 #124
by ci@centos.org 27 Oct '23

27 Oct '23
https://ci.centos.org/job/libvirt-perl-master-test/systems=libvirt-fedora-2… [...truncated 960 lines...] Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started 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-23 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-master-test/systems=libvirt-fedora-2…> [libvirt-fedora-23] $ /bin/sh -xe /tmp/hudson1724075579111103739.sh + make -j3 test TEST_MAINTAINER=1 PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/005-pod.t ............ ok # Failed test 'Pod coverage on Sys::Virt::Domain' # at /usr/share/perl5/vendor_perl/Test/Pod/Coverage.pm line 133. # Coverage for Sys::Virt::Domain is 99.9%, with 1 naked subroutine: # TUNABLE_BLKDEV_GROUP_NAME # Looks like you failed 1 test of 13. t/010-pod-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/13 subtests t/015-changes.t ........ ok t/020-constants.t ...... ok # Failed test 'VIR_PERF_PARAM_BRANCH_INSTRUCTIONS' # at t/030-api-coverage.t line 209. # Looks like you failed 1 test of 1526. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1526 subtests t/100-connect.t ........ ok t/200-domains.t ........ ok t/300-networks.t ....... ok t/400-storage-pools.t .. ok t/500-storage-vols.t ... ok t/600-interfaces.t ..... ok t/800-events.t ......... ok Test Summary Report ------------------- t/010-pod-coverage.t (Wstat: 256 Tests: 13 Failed: 1) Failed test: 8 Non-zero exit status: 1 t/030-api-coverage.t (Wstat: 256 Tests: 1526 Failed: 1) Failed test: 1507 Non-zero exit status: 1 Files=12, Tests=1778, 43 wallclock secs ( 0.47 usr 0.07 sys + 6.41 cusr 0.45 csys = 7.40 CPU) Result: FAIL Failed 2/12 test programs. 2/1778 subtests failed. Makefile:1030: recipe for target 'test_dynamic' failed make: *** [test_dynamic] Error 255 Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-test » libvirt-centos-7 #124
by ci@centos.org 27 Oct '23

27 Oct '23
https://ci.centos.org/job/libvirt-perl-master-test/systems=libvirt-centos-7… [...truncated 959 lines...] Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started 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-test/systems=libvirt-centos-7…> [libvirt-centos-7] $ /bin/sh -xe /tmp/hudson8956910059969782748.sh + make -j3 test TEST_MAINTAINER=1 PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/005-pod.t ............ ok # Failed test 'Pod coverage on Sys::Virt::Domain' # at /usr/share/perl5/vendor_perl/Test/Pod/Coverage.pm line 126. # Coverage for Sys::Virt::Domain is 99.9%, with 1 naked subroutine: # TUNABLE_BLKDEV_GROUP_NAME # Looks like you failed 1 test of 13. t/010-pod-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/13 subtests t/015-changes.t ........ ok t/020-constants.t ...... ok # Failed test 'VIR_PERF_PARAM_BRANCH_INSTRUCTIONS' # at t/030-api-coverage.t line 209. # Looks like you failed 1 test of 1526. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1526 subtests t/100-connect.t ........ ok t/200-domains.t ........ ok t/300-networks.t ....... ok t/400-storage-pools.t .. ok t/500-storage-vols.t ... ok t/600-interfaces.t ..... ok t/800-events.t ......... ok Test Summary Report ------------------- t/010-pod-coverage.t (Wstat: 256 Tests: 13 Failed: 1) Failed test: 13 Non-zero exit status: 1 t/030-api-coverage.t (Wstat: 256 Tests: 1526 Failed: 1) Failed test: 1507 Non-zero exit status: 1 Files=12, Tests=1778, 27 wallclock secs ( 0.33 usr 0.06 sys + 7.20 cusr 0.30 csys = 7.89 CPU) Result: FAIL Failed 2/12 test programs. 2/1778 subtests failed. make: *** [test_dynamic] Error 255 Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-build » libvirt-fedora-rawhide #138
by ci@centos.org 27 Oct '23

27 Oct '23
https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-fedora-…: [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-rawhide (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-fedora-…> > 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-rawhide] $ /bin/sh -xe /tmp/hudson4157914630626710844.sh + perl Makefile.PL PREFIX=/home/jenkins/build/libvirt libvirt >= 3.0.0 is required Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-build » libvirt-fedora-24 #138
by ci@centos.org 27 Oct '23

27 Oct '23
https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-fedora-…: [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-…> > 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
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-build » libvirt-fedora-23 #138
by ci@centos.org 27 Oct '23

27 Oct '23
https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-fedora-…: [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-23 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-fedora-…> > 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-23] $ /bin/sh -xe /tmp/hudson2607404446967673534.sh + perl Makefile.PL PREFIX=/home/jenkins/build/libvirt libvirt >= 3.0.0 is required Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-build » libvirt-centos-7 #138
by ci@centos.org 27 Oct '23

27 Oct '23
https://ci.centos.org/job/libvirt-perl-master-build/systems=libvirt-centos-…: [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-centos-…> > 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
1 2
0 0
  • ← Newer
  • 1
  • ...
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • ...
  • 75
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.