[Libvirt-ci] Build failed in Jenkins: libosinfo-master-syntax-check » libvirt #9

Thursday, 26 October 2023


https://ci.centos.org/job/libosinfo-master-syntax-check/systems=libvirt/9...
[...truncated 134 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 upstream project "osinfo-db-master-build" build number 6
  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
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started by an SCM change
   Started 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-22 (libvirt) in workspace
<https://ci.centos.org/job/libosinfo-master-syntax-check/systems=libvirt/w...
[libvirt] $ /bin/sh -xe /tmp/hudson2774709987001313825.sh
+ MAKE=make
++ uname
+ unamestr=Linux
+ '[' Linux = FreeBSD ']'
+ export OSINFO_DATA_DIR=/home/jenkins/build/libvirt/share/osinfo
+ OSINFO_DATA_DIR=/home/jenkins/build/libvirt/share/osinfo
+ cd build
/tmp/hudson2774709987001313825.sh: line 9: cd: build: No such file or directory
Build step 'Execute shell' marked build as failure

2024

2023

2022

2021

2020

2019

2018

2017

2016

[Libvirt-ci] Build failed in Jenkins: libosinfo-master-syntax-check » libvirt #9