- CI - libvirt List Archives

[Libvirt-ci] Build failed in Jenkins: libvirt-rpm » libvirt-centos-7 #355
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/355/display/…> ------------------------------------------ [...truncated 4.12 MB...] FAILED 281) cpuTestJSONSignature(x86_64): Opteron-6234 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 282) cpuTestUpdateLive(x86_64): Opteron-6234 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 283) cpuTestHostCPUID(x86_64): Opteron-6282 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 284) cpuTestGuestCPUID(x86_64): Opteron-6282 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 285) cpuTestCPUIDSignature(x86_64): Opteron-6282 ... OK 286) cpuTestHostCPUID(x86_64): Pentium-P6100 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 287) cpuTestGuestCPUID(x86_64): Pentium-P6100 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 288) cpuTestCPUIDSignature(x86_64): Pentium-P6100 ... OK 289) cpuTestHostCPUID(x86_64): Phenom-B95 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 290) cpuTestGuestCPUID(x86_64): Phenom-B95 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 291) cpuTestCPUIDSignature(x86_64): Phenom-B95 ... OK 292) cpuTestJSONCPUID(x86_64): Phenom-B95 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 293) cpuTestJSONSignature(x86_64): Phenom-B95 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 294) cpuTestUpdateLive(x86_64): Phenom-B95 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 295) cpuTestHostCPUID(x86_64): Ryzen-7-1800X-Eight-Core ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 296) cpuTestGuestCPUID(x86_64): Ryzen-7-1800X-Eight-Core ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 297) cpuTestCPUIDSignature(x86_64): Ryzen-7-1800X-Eight-Core ... OK 298) cpuTestJSONCPUID(x86_64): Ryzen-7-1800X-Eight-Core ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 299) cpuTestJSONSignature(x86_64): Ryzen-7-1800X-Eight-Core ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 300) cpuTestUpdateLive(x86_64): Ryzen-7-1800X-Eight-Core ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 301) cpuTestHostCPUID(x86_64): Xeon-5110 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 302) cpuTestGuestCPUID(x86_64): Xeon-5110 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 303) cpuTestCPUIDSignature(x86_64): Xeon-5110 ... OK 304) cpuTestHostCPUID(x86_64): Xeon-E3-1245-v5 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 305) cpuTestGuestCPUID(x86_64): Xeon-E3-1245-v5 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 306) cpuTestCPUIDSignature(x86_64): Xeon-E3-1245-v5 ... OK 307) cpuTestGuestCPUID(x86_64): Xeon-E3-1245-v5 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 308) cpuTestJSONCPUID(x86_64): Xeon-E3-1245-v5 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 309) cpuTestJSONSignature(x86_64): Xeon-E3-1245-v5 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 310) cpuTestUpdateLive(x86_64): Xeon-E3-1245-v5 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 311) cpuTestHostCPUID(x86_64): Xeon-E5-2609-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 312) cpuTestGuestCPUID(x86_64): Xeon-E5-2609-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 313) cpuTestCPUIDSignature(x86_64): Xeon-E5-2609-v3 ... OK 314) cpuTestGuestCPUID(x86_64): Xeon-E5-2609-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 315) cpuTestJSONCPUID(x86_64): Xeon-E5-2609-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 316) cpuTestJSONSignature(x86_64): Xeon-E5-2609-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 317) cpuTestUpdateLive(x86_64): Xeon-E5-2609-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 318) cpuTestHostCPUID(x86_64): Xeon-E5-2623-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 319) cpuTestGuestCPUID(x86_64): Xeon-E5-2623-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 320) cpuTestCPUIDSignature(x86_64): Xeon-E5-2623-v4 ... OK 321) cpuTestGuestCPUID(x86_64): Xeon-E5-2623-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 322) cpuTestJSONCPUID(x86_64): Xeon-E5-2623-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 323) cpuTestJSONSignature(x86_64): Xeon-E5-2623-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 324) cpuTestUpdateLive(x86_64): Xeon-E5-2623-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 325) cpuTestHostCPUID(x86_64): Xeon-E5-2630-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 326) cpuTestGuestCPUID(x86_64): Xeon-E5-2630-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 327) cpuTestCPUIDSignature(x86_64): Xeon-E5-2630-v3 ... OK 328) cpuTestJSONCPUID(x86_64): Xeon-E5-2630-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 329) cpuTestJSONSignature(x86_64): Xeon-E5-2630-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 330) cpuTestUpdateLive(x86_64): Xeon-E5-2630-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 331) cpuTestHostCPUID(x86_64): Xeon-E5-2630-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 332) cpuTestGuestCPUID(x86_64): Xeon-E5-2630-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 333) cpuTestCPUIDSignature(x86_64): Xeon-E5-2630-v4 ... OK 334) cpuTestGuestCPUID(x86_64): Xeon-E5-2630-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 335) cpuTestJSONCPUID(x86_64): Xeon-E5-2630-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 336) cpuTestJSONSignature(x86_64): Xeon-E5-2630-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 337) cpuTestUpdateLive(x86_64): Xeon-E5-2630-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 338) cpuTestHostCPUID(x86_64): Xeon-E5-2650 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 339) cpuTestGuestCPUID(x86_64): Xeon-E5-2650 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 340) cpuTestCPUIDSignature(x86_64): Xeon-E5-2650 ... OK 341) cpuTestGuestCPUID(x86_64): Xeon-E5-2650 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 342) cpuTestJSONCPUID(x86_64): Xeon-E5-2650 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 343) cpuTestJSONSignature(x86_64): Xeon-E5-2650 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 344) cpuTestUpdateLive(x86_64): Xeon-E5-2650 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 345) cpuTestHostCPUID(x86_64): Xeon-E5-2650-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 346) cpuTestGuestCPUID(x86_64): Xeon-E5-2650-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 347) cpuTestCPUIDSignature(x86_64): Xeon-E5-2650-v3 ... OK 348) cpuTestJSONCPUID(x86_64): Xeon-E5-2650-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 349) cpuTestJSONSignature(x86_64): Xeon-E5-2650-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 350) cpuTestUpdateLive(x86_64): Xeon-E5-2650-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 351) cpuTestHostCPUID(x86_64): Xeon-E5-2650-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 352) cpuTestGuestCPUID(x86_64): Xeon-E5-2650-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 353) cpuTestCPUIDSignature(x86_64): Xeon-E5-2650-v4 ... OK 354) cpuTestGuestCPUID(x86_64): Xeon-E5-2650-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 355) cpuTestJSONCPUID(x86_64): Xeon-E5-2650-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 356) cpuTestJSONSignature(x86_64): Xeon-E5-2650-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 357) cpuTestUpdateLive(x86_64): Xeon-E5-2650-v4 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 358) cpuTestHostCPUID(x86_64): Xeon-E7-4820 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 359) cpuTestGuestCPUID(x86_64): Xeon-E7-4820 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 360) cpuTestCPUIDSignature(x86_64): Xeon-E7-4820 ... OK 361) cpuTestJSONCPUID(x86_64): Xeon-E7-4820 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 362) cpuTestJSONSignature(x86_64): Xeon-E7-4820 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 363) cpuTestUpdateLive(x86_64): Xeon-E7-4820 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 364) cpuTestHostCPUID(x86_64): Xeon-E7-4830 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 365) cpuTestGuestCPUID(x86_64): Xeon-E7-4830 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 366) cpuTestCPUIDSignature(x86_64): Xeon-E7-4830 ... OK 367) cpuTestJSONCPUID(x86_64): Xeon-E7-4830 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 368) cpuTestJSONSignature(x86_64): Xeon-E7-4830 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 369) cpuTestUpdateLive(x86_64): Xeon-E7-4830 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 370) cpuTestHostCPUID(x86_64): Xeon-E7-8890-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 371) cpuTestGuestCPUID(x86_64): Xeon-E7-8890-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 372) cpuTestCPUIDSignature(x86_64): Xeon-E7-8890-v3 ... OK 373) cpuTestGuestCPUID(x86_64): Xeon-E7-8890-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 374) cpuTestJSONCPUID(x86_64): Xeon-E7-8890-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 375) cpuTestJSONSignature(x86_64): Xeon-E7-8890-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 376) cpuTestUpdateLive(x86_64): Xeon-E7-8890-v3 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 377) cpuTestHostCPUID(x86_64): Xeon-E7540 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 378) cpuTestGuestCPUID(x86_64): Xeon-E7540 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 379) cpuTestCPUIDSignature(x86_64): Xeon-E7540 ... OK 380) cpuTestGuestCPUID(x86_64): Xeon-E7540 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 381) cpuTestJSONCPUID(x86_64): Xeon-E7540 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 382) cpuTestJSONSignature(x86_64): Xeon-E7540 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 383) cpuTestUpdateLive(x86_64): Xeon-E7540 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 384) cpuTestHostCPUID(x86_64): Xeon-Gold-5115 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 385) cpuTestGuestCPUID(x86_64): Xeon-Gold-5115 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 386) cpuTestCPUIDSignature(x86_64): Xeon-Gold-5115 ... OK 387) cpuTestGuestCPUID(x86_64): Xeon-Gold-5115 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 388) cpuTestJSONCPUID(x86_64): Xeon-Gold-5115 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 389) cpuTestJSONSignature(x86_64): Xeon-Gold-5115 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 390) cpuTestUpdateLive(x86_64): Xeon-Gold-5115 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 391) cpuTestHostCPUID(x86_64): Xeon-Gold-6148 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 392) cpuTestGuestCPUID(x86_64): Xeon-Gold-6148 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 393) cpuTestCPUIDSignature(x86_64): Xeon-Gold-6148 ... OK 394) cpuTestJSONCPUID(x86_64): Xeon-Gold-6148 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 395) cpuTestJSONSignature(x86_64): Xeon-Gold-6148 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 396) cpuTestUpdateLive(x86_64): Xeon-Gold-6148 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 397) cpuTestHostCPUID(x86_64): Xeon-Platinum-8268 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 398) cpuTestGuestCPUID(x86_64): Xeon-Platinum-8268 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 399) cpuTestCPUIDSignature(x86_64): Xeon-Platinum-8268 ... OK 400) cpuTestJSONCPUID(x86_64): Xeon-Platinum-8268 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 401) cpuTestJSONSignature(x86_64): Xeon-Platinum-8268 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 402) cpuTestUpdateLive(x86_64): Xeon-Platinum-8268 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 403) cpuTestHostCPUID(x86_64): Xeon-W3520 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 404) cpuTestGuestCPUID(x86_64): Xeon-W3520 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 405) cpuTestCPUIDSignature(x86_64): Xeon-W3520 ... OK 406) cpuTestJSONCPUID(x86_64): Xeon-W3520 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 407) cpuTestJSONSignature(x86_64): Xeon-W3520 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 408) cpuTestUpdateLive(x86_64): Xeon-W3520 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 409) cpuTestHostCPUID(x86_64): Xeon-X5460 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 410) cpuTestGuestCPUID(x86_64): Xeon-X5460 ... libvirt: CPU Driver error : XML error: failed to parse xml document '<https://ci.centos.org/job/libvirt-rpm/systems=libvirt-centos-7/ws/build/rpm…'> FAILED 411) cpuTestCPUIDSignature(x86_64): Xeon-X5460 ... OK + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.NyUPVM (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.NyUPVM (%check) Build step 'Execute shell' marked build as failure

1 2

[Libvirt-ci] Build failed in Jenkins: libvirt-dbus-check » libvirt-fedora-29 #327
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/327/…> ------------------------------------------ Started by upstream project "libvirt-dbus-check" build number 327 originally caused by: Started by upstream project "libvirt-dbus-syntax-check" build number 370 originally caused by: Started by upstream project "libvirt-dbus-build" build number 377 originally caused by: Started by upstream project "libvirt-glib-build" build number 374 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/> [libvirt-dbus] $ /bin/sh -xe /tmp/jenkins4930337592210177912.sh + cd build + /usr/bin/gmake check Making check in data gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> Making check in docs gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> Making check in src gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> Making check in tests gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> /usr/bin/gmake test_util gmake[2]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> CC test_util-test_util.o CCLD test_util gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> /usr/bin/gmake check-TESTS gmake[2]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> gmake[3]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> PASS: test_util PASS: test_interface.py PASS: test_domain.py PASS: test_network.py PASS: test_nodedev.py FAIL: test_connect.py PASS: test_storage.py ============================================================================ Testsuite summary for libvirt-dbus 1.4.0 ============================================================================ # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/test-suite.log Please report to libvir-list(a)redhat.com ============================================================================ gmake[3]: *** [Makefile:766: test-suite.log] Error 1 gmake[3]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> gmake[2]: *** [Makefile:874: check-TESTS] Error 2 gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> gmake[1]: *** [Makefile:990: check-am] Error 2 gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/b…'> gmake: *** [Makefile:460: check-recursive] Error 1 + cat tests/test-suite.log ============================================== libvirt-dbus 1.4.0: tests/test-suite.log ============================================== # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test_connect.py ===================== ============================= test session starts ============================== platform linux -- Python 3.7.2, pytest-3.6.4, py-1.5.4, pluggy-0.6.0 rootdir: <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-29/ws/,> inifile: collected 35 items ../../tests/test_connect.py ..................F................ [100%] =================================== FAILURES =================================== _________________ TestConnect.test_connect_get_cpu_model_names _________________ self = <test_connect.TestConnect object at 0x7eff07e599b0> def test_connect_get_cpu_model_names(self): arch = "x86_64" > assert isinstance(self.connect.GetCPUModelNames(arch, 0), dbus.Array) ../../tests/test_connect.py:122: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib64/python3.7/site-packages/dbus/proxies.py:70: in __call__ return self._proxy_method(*args, **keywords) /usr/lib64/python3.7/site-packages/dbus/proxies.py:145: in __call__ **keywords) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <dbus._dbus.SessionBus (session) at 0x7eff07ef4728> bus_name = dbus.String(':1.19'), object_path = '/org/libvirt/Test' dbus_interface = 'org.libvirt.Connect', method = 'GetCPUModelNames' signature = 'su', args = ('x86_64', 0), timeout = -1.0, byte_arrays = False kwargs = {}, get_args_opts = {'byte_arrays': False} message = <dbus.lowlevel.MethodCallMessage path: /org/libvirt/Test, iface: org.libvirt.Connect, member: GetCPUModelNames dest: :1.19> def call_blocking(self, bus_name, object_path, dbus_interface, method, signature, args, timeout=-1.0, byte_arrays=False, **kwargs): """Call the given method, synchronously. :Since: 0.81.0 """ if object_path == LOCAL_PATH: raise DBusException('Methods may not be called on the reserved ' 'path %s' % LOCAL_PATH) if dbus_interface == LOCAL_IFACE: raise DBusException('Methods may not be called on the reserved ' 'interface %s' % LOCAL_IFACE) # no need to validate other args - MethodCallMessage ctor will do get_args_opts = dict(byte_arrays=byte_arrays) if is_py2: get_args_opts['utf8_strings'] = kwargs.get('utf8_strings', False) elif 'utf8_strings' in kwargs: raise TypeError("unexpected keyword argument 'utf8_strings'") message = MethodCallMessage(destination=bus_name, path=object_path, interface=dbus_interface, method=method) # Add the arguments to the function try: message.append(signature=signature, *args) except Exception as e: logging.basicConfig() _logger.error('Unable to set arguments %r according to ' 'signature %r: %s: %s', args, signature, e.__class__, e) raise # make a blocking call reply_message = self.send_message_with_reply_and_block( > message, timeout) E dbus.exceptions.DBusException: org.libvirt.Error: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' /usr/lib64/python3.7/site-packages/dbus/connection.py:651: DBusException ----------------------------- Captured stderr call ----------------------------- I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" ===================== 1 failed, 34 passed in 14.54 seconds ===================== FAIL test_connect.py (exit status: 1) + exit 1 Build step 'Execute shell' marked build as failure

1 2

[Libvirt-ci] Build failed in Jenkins: libvirt-dbus-check » libvirt-fedora-28 #327
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/327/…> ------------------------------------------ Started by upstream project "libvirt-dbus-check" build number 327 originally caused by: Started by upstream project "libvirt-dbus-syntax-check" build number 370 originally caused by: Started by upstream project "libvirt-dbus-build" build number 377 originally caused by: Started by upstream project "libvirt-glib-build" build number 374 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-28 (libvirt) in workspace <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/> [libvirt-dbus] $ /bin/sh -xe /tmp/jenkins408357717686316263.sh + cd build + /usr/bin/gmake check Making check in data gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> Making check in docs gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> Making check in src gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> Making check in tests gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> /usr/bin/gmake test_util gmake[2]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> CC test_util-test_util.o CCLD test_util gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> /usr/bin/gmake check-TESTS gmake[2]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> gmake[3]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> PASS: test_util PASS: test_interface.py PASS: test_domain.py PASS: test_network.py PASS: test_nodedev.py FAIL: test_connect.py PASS: test_storage.py ============================================================================ Testsuite summary for libvirt-dbus 1.4.0 ============================================================================ # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/test-suite.log Please report to libvir-list(a)redhat.com ============================================================================ gmake[3]: *** [Makefile:759: test-suite.log] Error 1 gmake[3]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> gmake[2]: *** [Makefile:867: check-TESTS] Error 2 gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> gmake[1]: *** [Makefile:980: check-am] Error 2 gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/b…'> gmake: *** [Makefile:460: check-recursive] Error 1 + cat tests/test-suite.log ============================================== libvirt-dbus 1.4.0: tests/test-suite.log ============================================== # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test_connect.py ===================== ============================= test session starts ============================== platform linux -- Python 3.6.8, pytest-3.4.2, py-1.5.4, pluggy-0.6.0 rootdir: <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-28/ws/,> inifile: collected 35 items ../../tests/test_connect.py ..................F................ [100%] =================================== FAILURES =================================== _________________ TestConnect.test_connect_get_cpu_model_names _________________ self = <test_connect.TestConnect object at 0x7fee8fed9be0> def test_connect_get_cpu_model_names(self): arch = "x86_64" > assert isinstance(self.connect.GetCPUModelNames(arch, 0), dbus.Array) ../../tests/test_connect.py:122: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib64/python3.6/site-packages/dbus/proxies.py:70: in __call__ return self._proxy_method(*args, **keywords) /usr/lib64/python3.6/site-packages/dbus/proxies.py:145: in __call__ **keywords) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <dbus._dbus.SessionBus (session) at 0x7fee8ff37150> bus_name = dbus.String(':1.19'), object_path = '/org/libvirt/Test' dbus_interface = 'org.libvirt.Connect', method = 'GetCPUModelNames' signature = 'su', args = ('x86_64', 0), timeout = -1.0, byte_arrays = False kwargs = {}, get_args_opts = {'byte_arrays': False} message = <dbus.lowlevel.MethodCallMessage path: /org/libvirt/Test, iface: org.libvirt.Connect, member: GetCPUModelNames dest: :1.19> def call_blocking(self, bus_name, object_path, dbus_interface, method, signature, args, timeout=-1.0, byte_arrays=False, **kwargs): """Call the given method, synchronously. :Since: 0.81.0 """ if object_path == LOCAL_PATH: raise DBusException('Methods may not be called on the reserved ' 'path %s' % LOCAL_PATH) if dbus_interface == LOCAL_IFACE: raise DBusException('Methods may not be called on the reserved ' 'interface %s' % LOCAL_IFACE) # no need to validate other args - MethodCallMessage ctor will do get_args_opts = dict(byte_arrays=byte_arrays) if is_py2: get_args_opts['utf8_strings'] = kwargs.get('utf8_strings', False) elif 'utf8_strings' in kwargs: raise TypeError("unexpected keyword argument 'utf8_strings'") message = MethodCallMessage(destination=bus_name, path=object_path, interface=dbus_interface, method=method) # Add the arguments to the function try: message.append(signature=signature, *args) except Exception as e: logging.basicConfig() _logger.error('Unable to set arguments %r according to ' 'signature %r: %s: %s', args, signature, e.__class__, e) raise # make a blocking call reply_message = self.send_message_with_reply_and_block( > message, timeout) E dbus.exceptions.DBusException: org.libvirt.Error: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' /usr/lib64/python3.6/site-packages/dbus/connection.py:651: DBusException ----------------------------- Captured stderr call ----------------------------- I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" ===================== 1 failed, 34 passed in 16.25 seconds ===================== FAIL test_connect.py (exit status: 1) + exit 1 Build step 'Execute shell' marked build as failure

1 2

[Libvirt-ci] Build failed in Jenkins: libvirt-dbus-check » libvirt-debian-9 #327
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/327/d…> ------------------------------------------ Started by upstream project "libvirt-dbus-check" build number 327 originally caused by: Started by upstream project "libvirt-dbus-syntax-check" build number 370 originally caused by: Started by upstream project "libvirt-dbus-build" build number 377 originally caused by: Started by upstream project "libvirt-glib-build" build number 374 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/> [libvirt-dbus] $ /bin/sh -xe /tmp/jenkins4327428844215728392.sh + cd build + /usr/bin/make check Making check in data make[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> Making check in docs make[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> Making check in src make[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> Making check in tests make[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> /usr/bin/make test_util make[2]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> CC test_util-test_util.o CCLD test_util make[2]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> /usr/bin/make check-TESTS make[2]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> make[3]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> PASS: test_util PASS: test_interface.py PASS: test_domain.py PASS: test_network.py PASS: test_nodedev.py FAIL: test_connect.py PASS: test_storage.py ============================================================================ Testsuite summary for libvirt-dbus 1.4.0 ============================================================================ # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/test-suite.log Please report to libvir-list(a)redhat.com ============================================================================ Makefile:759: recipe for target 'test-suite.log' failed make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> Makefile:865: recipe for target 'check-TESTS' failed make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> Makefile:980: recipe for target 'check-am' failed make[1]: *** [check-am] Error 2 make[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/bu…'> Makefile:461: recipe for target 'check-recursive' failed make: *** [check-recursive] Error 1 + cat tests/test-suite.log ============================================== libvirt-dbus 1.4.0: tests/test-suite.log ============================================== # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test_connect.py ===================== ============================= test session starts ============================== platform linux -- Python 3.5.3, pytest-3.0.6, py-1.4.32, pluggy-0.4.0 rootdir: <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-debian-9/ws/,> inifile: collected 35 items ../../tests/test_connect.py ..................F................ =================================== FAILURES =================================== _________________ TestConnect.test_connect_get_cpu_model_names _________________ self = <test_connect.TestConnect object at 0x7fefb631d1d0> def test_connect_get_cpu_model_names(self): arch = "x86_64" > assert isinstance(self.connect.GetCPUModelNames(arch, 0), dbus.Array) ../../tests/test_connect.py:122: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python3/dist-packages/dbus/proxies.py:70: in __call__ return self._proxy_method(*args, **keywords) /usr/lib/python3/dist-packages/dbus/proxies.py:145: in __call__ **keywords) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <dbus._dbus.SessionBus (session) at 0x7fefb60547d8> bus_name = dbus.String(':1.19'), object_path = '/org/libvirt/Test' dbus_interface = 'org.libvirt.Connect', method = 'GetCPUModelNames' signature = 'su', args = ('x86_64', 0), timeout = -1.0, byte_arrays = False kwargs = {}, get_args_opts = {'byte_arrays': False} message = <dbus.lowlevel.MethodCallMessage path: /org/libvirt/Test, iface: org.libvirt.Connect, member: GetCPUModelNames dest: :1.19> def call_blocking(self, bus_name, object_path, dbus_interface, method, signature, args, timeout=-1.0, byte_arrays=False, **kwargs): """Call the given method, synchronously. :Since: 0.81.0 """ if object_path == LOCAL_PATH: raise DBusException('Methods may not be called on the reserved ' 'path %s' % LOCAL_PATH) if dbus_interface == LOCAL_IFACE: raise DBusException('Methods may not be called on the reserved ' 'interface %s' % LOCAL_IFACE) # no need to validate other args - MethodCallMessage ctor will do get_args_opts = dict(byte_arrays=byte_arrays) if is_py2: get_args_opts['utf8_strings'] = kwargs.get('utf8_strings', False) elif 'utf8_strings' in kwargs: raise TypeError("unexpected keyword argument 'utf8_strings'") message = MethodCallMessage(destination=bus_name, path=object_path, interface=dbus_interface, method=method) # Add the arguments to the function try: message.append(signature=signature, *args) except Exception as e: logging.basicConfig() _logger.error('Unable to set arguments %r according to ' 'signature %r: %s: %s', args, signature, e.__class__, e) raise # make a blocking call reply_message = self.send_message_with_reply_and_block( > message, timeout) E dbus.exceptions.DBusException: org.libvirt.Error: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' /usr/lib/python3/dist-packages/dbus/connection.py:651: DBusException ----------------------------- Captured stderr call ----------------------------- I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" ===================== 1 failed, 34 passed in 9.00 seconds ====================== FAIL test_connect.py (exit status: 1) + exit 1 Build step 'Execute shell' marked build as failure

1 2

[Libvirt-ci] Build failed in Jenkins: virt-manager-check » libvirt-fedora-rawhide #636
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-rawhide…> ------------------------------------------ Started by upstream project "virt-manager-check" build number 636 originally caused by: Started by upstream project "virt-manager-build" build number 639 originally caused by: Started by upstream project "libvirt-python-build" build number 386 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-rawhide (libvirt) in workspace <https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-rawhide…> [virt-manager] $ /bin/sh -xe /tmp/jenkins2117385379692922130.sh + /usr/bin/python3 ./setup.py test running test .........................................................................................................I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" .......................................F..............................................................................................................................................................................................................................................................................................................................................sssssssssssssssssss ====================================================================== FAIL: testCLI0018virt_install_cpu_rhel7_default (tests.clitest.CLITests) ---------------------------------------------------------------------- Traceback (most recent call last): File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-rawhide…",> line 1209, in <lambda> return lambda s: cmdtemplate(s, cmd) File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-rawhide…",> line 1208, in cmdtemplate _cmdobj.run(self) File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-rawhide…",> line 269, in run tests.fail(err) AssertionError: ./virt-install --name foobar --ram 64 --print-step all --hvm --nographics --noautoconsole --nodisks --pxe --connect __virtinst_test__test://<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-rawhide…> Conversion outputs did not match. --- tests/cli-test-xml/compare/virt-install-cpu-rhel7-default.xml +++ Generated Output @@ -14,8 +14,6 @@ </features> <cpu mode="custom" match="exact"> <model>Skylake-Client-IBRS</model> - <feature policy="require" name="spec-ctrl"/> - <feature policy="require" name="ssbd"/> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> @@ -63,8 +61,6 @@ </features> <cpu mode="custom" match="exact"> <model>Skylake-Client-IBRS</model> - <feature policy="require" name="spec-ctrl"/> - <feature policy="require" name="ssbd"/> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> ---------------------------------------------------------------------- Ran 498 tests in 136.310s FAILED (failures=1, skipped=19) Build step 'Execute shell' marked build as failure

1 2

[Libvirt-ci] Build failed in Jenkins: virt-manager-check » libvirt-fedora-28 #636
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-28/636/…> ------------------------------------------ Started by upstream project "virt-manager-check" build number 636 originally caused by: Started by upstream project "virt-manager-build" build number 639 originally caused by: Started by upstream project "libvirt-python-build" build number 386 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-28 (libvirt) in workspace <https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-28/ws/> [virt-manager] $ /bin/sh -xe /tmp/jenkins6692235798583864133.sh + /usr/bin/python3 ./setup.py test running test .........................................................................................................I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" .......................................F..............................................................................................................................................................................................................................................................................................................................................sssssssssssssssssss ====================================================================== FAIL: testCLI0018virt_install_cpu_rhel7_default (tests.clitest.CLITests) ---------------------------------------------------------------------- Traceback (most recent call last): File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-28/ws/t…",> line 1209, in <lambda> return lambda s: cmdtemplate(s, cmd) File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-28/ws/t…",> line 1208, in cmdtemplate _cmdobj.run(self) File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-28/ws/t…",> line 269, in run tests.fail(err) AssertionError: ./virt-install --name foobar --ram 64 --print-step all --hvm --nographics --noautoconsole --nodisks --pxe --connect __virtinst_test__test://<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-28/ws/t…> Conversion outputs did not match. --- tests/cli-test-xml/compare/virt-install-cpu-rhel7-default.xml +++ Generated Output @@ -14,8 +14,6 @@ </features> <cpu mode="custom" match="exact"> <model>Skylake-Client-IBRS</model> - <feature policy="require" name="spec-ctrl"/> - <feature policy="require" name="ssbd"/> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> @@ -63,8 +61,6 @@ </features> <cpu mode="custom" match="exact"> <model>Skylake-Client-IBRS</model> - <feature policy="require" name="spec-ctrl"/> - <feature policy="require" name="ssbd"/> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> ---------------------------------------------------------------------- Ran 498 tests in 65.825s FAILED (failures=1, skipped=19) Build step 'Execute shell' marked build as failure

1 2

[Libvirt-ci] Build failed in Jenkins: virt-manager-check » libvirt-fedora-29 #636
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-29/636/…> ------------------------------------------ Started by upstream project "virt-manager-check" build number 636 originally caused by: Started by upstream project "virt-manager-build" build number 639 originally caused by: Started by upstream project "libvirt-python-build" build number 386 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-29/ws/> [virt-manager] $ /bin/sh -xe /tmp/jenkins2133766135291068849.sh + /usr/bin/python3 ./setup.py test running test .........................................................................................................I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" .......................................F..............................................................................................................................................................................................................................................................................................................................................sssssssssssssssssss ====================================================================== FAIL: testCLI0018virt_install_cpu_rhel7_default (tests.clitest.CLITests) ---------------------------------------------------------------------- Traceback (most recent call last): File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-29/ws/t…",> line 1209, in <lambda> return lambda s: cmdtemplate(s, cmd) File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-29/ws/t…",> line 1208, in cmdtemplate _cmdobj.run(self) File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-29/ws/t…",> line 269, in run tests.fail(err) AssertionError: ./virt-install --name foobar --ram 64 --print-step all --hvm --nographics --noautoconsole --nodisks --pxe --connect __virtinst_test__test://<https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-29/ws/t…> Conversion outputs did not match. --- tests/cli-test-xml/compare/virt-install-cpu-rhel7-default.xml +++ Generated Output @@ -14,8 +14,6 @@ </features> <cpu mode="custom" match="exact"> <model>Skylake-Client-IBRS</model> - <feature policy="require" name="spec-ctrl"/> - <feature policy="require" name="ssbd"/> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> @@ -63,8 +61,6 @@ </features> <cpu mode="custom" match="exact"> <model>Skylake-Client-IBRS</model> - <feature policy="require" name="spec-ctrl"/> - <feature policy="require" name="ssbd"/> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> ---------------------------------------------------------------------- Ran 498 tests in 49.992s FAILED (failures=1, skipped=19) Build step 'Execute shell' marked build as failure

1 2

[Libvirt-ci] Build failed in Jenkins: virt-manager-check » libvirt-debian-9 #636
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/636/d…> ------------------------------------------ Started by upstream project "virt-manager-check" build number 636 originally caused by: Started by upstream project "virt-manager-build" build number 639 originally caused by: Started by upstream project "libvirt-python-build" build number 386 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-9 (libvirt) in workspace <https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/> [virt-manager] $ /bin/sh -xe /tmp/jenkins6090044919285261988.sh + /usr/bin/python3 ./setup.py test running test .........................................................................................................I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" .......................................F..............................................................................................................................................................................................................................................................................................................................................sssssssssssssssssss ====================================================================== FAIL: testCLI0018virt_install_cpu_rhel7_default (tests.clitest.CLITests) ---------------------------------------------------------------------- Traceback (most recent call last): File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/te…",> line 1209, in <lambda> return lambda s: cmdtemplate(s, cmd) File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/te…",> line 1208, in cmdtemplate _cmdobj.run(self) File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/te…",> line 269, in run tests.fail(err) AssertionError: ./virt-install --name foobar --ram 64 --print-step all --hvm --nographics --noautoconsole --nodisks --pxe --connect __virtinst_test__test://<https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/te…> Conversion outputs did not match. --- tests/cli-test-xml/compare/virt-install-cpu-rhel7-default.xml +++ Generated Output @@ -14,8 +14,6 @@ </features> <cpu mode="custom" match="exact"> <model>Skylake-Client-IBRS</model> - <feature policy="require" name="spec-ctrl"/> - <feature policy="require" name="ssbd"/> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> @@ -63,8 +61,6 @@ </features> <cpu mode="custom" match="exact"> <model>Skylake-Client-IBRS</model> - <feature policy="require" name="spec-ctrl"/> - <feature policy="require" name="ssbd"/> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> ---------------------------------------------------------------------- Ran 498 tests in 46.678s FAILED (failures=1, skipped=19) Build step 'Execute shell' marked build as failure

1 2

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-rawhide #383
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-rawhide…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 383 originally caused by: Started by upstream project "libvirt-perl-build" build number 384 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: 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-check/systems=libvirt-fedora-rawhide…> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins5927694276280101092.sh + export TEST_MAINTAINER=1 + TEST_MAINTAINER=1 + perl Build test t/005-pod.t ............ ok t/010-pod-coverage.t ... ok t/015-changes.t ........ ok t/020-constants.t ...... ok t/030-api-coverage.t ... ok I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" libvirt error code: 27, message: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' # Looks like your test exited with 2 just after 24. t/100-connect.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/25 subtests (less 1 skipped subtest: 23 okay) 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/100-connect.t (Wstat: 512 Tests: 24 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 25 tests but ran 24. Files=12, Tests=1913, 78 wallclock secs ( 0.56 usr 0.19 sys + 10.08 cusr 2.49 csys = 13.32 CPU) Result: FAIL Failed 1/12 test programs. 0/1913 subtests failed. Build step 'Execute shell' marked build as failure

1 2

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-debian-9 #383
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/383/d…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 383 originally caused by: Started by upstream project "libvirt-perl-build" build number 384 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins6594927893069111220.sh + export TEST_MAINTAINER=1 + perl Build test t/005-pod.t ............ ok t/010-pod-coverage.t ... ok t/015-changes.t ........ ok t/020-constants.t ...... ok t/030-api-coverage.t ... ok I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" libvirt error code: 27, message: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' # Looks like you planned 25 tests but ran 24. # Looks like your test exited with 2 just after 24. t/100-connect.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/25 subtests (less 1 skipped subtest: 23 okay) 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/100-connect.t (Wstat: 512 Tests: 24 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 25 tests but ran 24. Files=12, Tests=1913, 29 wallclock secs ( 0.52 usr 0.07 sys + 8.89 cusr 0.52 csys = 10.00 CPU) Result: FAIL Failed 1/12 test programs. 0/1913 subtests failed. Build step 'Execute shell' marked build as failure

1 2