- CI - libvirt List Archives

[Libvirt-ci] Build failed in Jenkins: osinfo-db-tools-syntax-check » libvirt-fedora-29 #19
by ci＠centos.org 16 Apr '19

16 Apr '19

See <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-fedo…> ------------------------------------------ Started by upstream project "osinfo-db-tools-syntax-check" build number 19 originally caused by: Started by upstream project "osinfo-db-tools-build" build number 20 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-fedo…> [osinfo-db-tools] $ /bin/sh -xe /tmp/jenkins1453706994515087149.sh + cd build + /usr/bin/gmake syntax-check GFDL_version Wundef_boolean TAB_in_indentation avoid_if_before_free avoid_attribute_unused_in_header bindtextdomain bracket_spacing_check cast_of_argument_to_free cast_of_x_alloc_return_value changelog const_long_option copyright_check copyright_format error_message_period error_message_warn_fatal m4_quote_check makefile_TAB_only_indentation makefile_at_at_check makefile_path_separator_check obsolete_symbols po_check preprocessor_indentation prohibit_HAVE_MBRTOWC prohibit_S_IS_definition prohibit_always-defined_macros prohibit_argmatch_without_use prohibit_assert_without_use prohibit_atoi_atof prohibit_backup_files prohibit_c_ctype_without_use prohibit_canonicalize_without_use prohibit_cloexec_without_use prohibit_close_stream_without_use prohibit_cvs_keyword prohibit_defined_have_decl_tests prohibit_dirent_without_use prohibit_doubled_word prohibit_empty_lines_at_EOF prohibit_error_without_use prohibit_getopt_without_use prohibit_hash_pjw_without_use prohibit_hash_without_use prohibit_have_config_h prohibit_ignore_value_without_use prohibit_intprops_without_use prohibit_inttostr_without_use prohibit_long_options_without_use prohibit_magic_number_exit prohibit_openat_without_use prohibit_path_max_allocation prohibit_posixver_without_use prohibit_quote_without_use prohibit_quotearg_without_use prohibit_reversed_compare_failure prohibit_root_dev_ino_without_use prohibit_safe_read_without_use prohibit_same_without_use prohibit_signal_without_use prohibit_stat_st_blocks prohibit_stddef_without_use prohibit_stdio--_without_use prohibit_stdio-safer_without_use prohibit_strcmp prohibit_strings_without_use prohibit_strncpy prohibit_test_double_equal prohibit_test_minus_ao prohibit_verify_without_use prohibit_undesirable_word_seq prohibit_xalloc_without_use prohibit_xfreopen_without_use proper_name_utf8_requires_ICONV redundant_const require_config_h require_config_h_first require_test_exit_idiom space_tab texinfo_acronym tight_scope trailing_blank unmarked_diagnostics useless_cpp_parens vulnerable_makefile_CVE-2009-4029 vulnerable_makefile_CVE-2012-3386 GEN sc_bracket_spacing_check ../configure.ac:35:AM_CONDITIONAL([EXECUTE_TESTS], [test "x$HAVE_PYTEST" == "xyes" -a "x$HAVE_REQUESTS" = "xyes"]) maint.mk: use "test C1 && test C2", not "test C1 -a C2"; use "test C1 || test C2", not "test C1 -o C2" gmake: *** [../maint.mk:1002: sc_prohibit_test_minus_ao] Error 1 gmake: *** Waiting for unfinished jobs.... Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: osinfo-db-tools-syntax-check » libvirt-freebsd-11 #19
by ci＠centos.org 16 Apr '19

16 Apr '19

See <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-free…> ------------------------------------------ Started by upstream project "osinfo-db-tools-syntax-check" build number 19 originally caused by: Started by upstream project "osinfo-db-tools-build" build number 20 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-freebsd-11 (libvirt) in workspace <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-free…> [osinfo-db-tools] $ /bin/sh -xe /tmp/jenkins3238859452746174097.sh + cd build + /usr/local/bin/gmake syntax-check GFDL_version TAB_in_indentation Wundef_boolean avoid_attribute_unused_in_header avoid_if_before_free bindtextdomain cast_of_argument_to_free cast_of_x_alloc_return_value bracket_spacing_check changelog const_long_option error_message_period error_message_warn_fatal m4_quote_check makefile_TAB_only_indentation makefile_at_at_check makefile_path_separator_check obsolete_symbols po_check copyright_check copyright_format preprocessor_indentation prohibit_HAVE_MBRTOWC prohibit_S_IS_definition prohibit_always-defined_macros prohibit_argmatch_without_use prohibit_atoi_atof prohibit_assert_without_use prohibit_backup_files prohibit_c_ctype_without_use prohibit_canonicalize_without_use prohibit_cloexec_without_use prohibit_close_stream_without_use prohibit_cvs_keyword prohibit_defined_have_decl_tests prohibit_dirent_without_use prohibit_doubled_word prohibit_empty_lines_at_EOF prohibit_error_without_use prohibit_getopt_without_use prohibit_hash_pjw_without_use prohibit_hash_without_use prohibit_ignore_value_without_use prohibit_intprops_without_use prohibit_inttostr_without_use prohibit_have_config_h prohibit_long_options_without_use prohibit_magic_number_exit prohibit_openat_without_use prohibit_posixver_without_use prohibit_path_max_allocation prohibit_quote_without_use prohibit_quotearg_without_use prohibit_reversed_compare_failure prohibit_root_dev_ino_without_use prohibit_safe_read_without_use prohibit_signal_without_use prohibit_same_without_use prohibit_stat_st_blocks prohibit_stddef_without_use prohibit_stdio--_without_use prohibit_stdio-safer_without_use prohibit_strcmp prohibit_strings_without_use prohibit_test_double_equal prohibit_strncpy prohibit_test_minus_ao prohibit_undesirable_word_seq prohibit_xalloc_without_use prohibit_verify_without_use prohibit_xfreopen_without_use proper_name_utf8_requires_ICONV redundant_const require_config_h require_config_h_first require_test_exit_idiom space_tab texinfo_acronym tight_scope trailing_blank useless_cpp_parens unmarked_diagnostics vulnerable_makefile_CVE-2009-4029 vulnerable_makefile_CVE-2012-3386 GEN sc_bracket_spacing_check ../configure.ac:35:AM_CONDITIONAL([EXECUTE_TESTS], [test "x$HAVE_PYTEST" == "xyes" -a "x$HAVE_REQUESTS" = "xyes"]) maint.mk: use "test C1 && test C2", not "test C1 -a C2"; use "test C1 || test C2", not "test C1 -o C2" gmake: *** [../maint.mk:1002: sc_prohibit_test_minus_ao] Error 1 gmake: *** Waiting for unfinished jobs.... Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: osinfo-db-tools-syntax-check » libvirt-freebsd-12 #19
by ci＠centos.org 16 Apr '19

16 Apr '19

See <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-free…> ------------------------------------------ Started by upstream project "osinfo-db-tools-syntax-check" build number 19 originally caused by: Started by upstream project "osinfo-db-tools-build" build number 20 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-freebsd-12 (libvirt) in workspace <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-free…> [osinfo-db-tools] $ /bin/sh -xe /tmp/jenkins6854513955049200741.sh + cd build + /usr/local/bin/gmake syntax-check GFDL_version TAB_in_indentation Wundef_boolean avoid_attribute_unused_in_header avoid_if_before_free bindtextdomain bracket_spacing_check cast_of_argument_to_free cast_of_x_alloc_return_value const_long_option copyright_check changelog copyright_format error_message_period error_message_warn_fatal m4_quote_check makefile_TAB_only_indentation makefile_at_at_check makefile_path_separator_check obsolete_symbols po_check prohibit_HAVE_MBRTOWC prohibit_S_IS_definition preprocessor_indentation prohibit_always-defined_macros prohibit_argmatch_without_use prohibit_assert_without_use prohibit_backup_files prohibit_c_ctype_without_use prohibit_atoi_atof prohibit_canonicalize_without_use prohibit_cloexec_without_use prohibit_close_stream_without_use prohibit_defined_have_decl_tests prohibit_cvs_keyword prohibit_dirent_without_use prohibit_doubled_word prohibit_empty_lines_at_EOF prohibit_error_without_use prohibit_getopt_without_use prohibit_hash_pjw_without_use prohibit_hash_without_use prohibit_have_config_h prohibit_intprops_without_use prohibit_ignore_value_without_use prohibit_long_options_without_use prohibit_inttostr_without_use prohibit_magic_number_exit prohibit_openat_without_use prohibit_path_max_allocation prohibit_posixver_without_use prohibit_quote_without_use prohibit_quotearg_without_use prohibit_reversed_compare_failure prohibit_root_dev_ino_without_use prohibit_safe_read_without_use prohibit_same_without_use prohibit_signal_without_use prohibit_stat_st_blocks prohibit_stddef_without_use prohibit_stdio--_without_use prohibit_stdio-safer_without_use prohibit_strcmp prohibit_strings_without_use prohibit_strncpy prohibit_test_double_equal prohibit_test_minus_ao prohibit_undesirable_word_seq prohibit_verify_without_use prohibit_xalloc_without_use prohibit_xfreopen_without_use proper_name_utf8_requires_ICONV redundant_const require_config_h require_config_h_first space_tab require_test_exit_idiom texinfo_acronym tight_scope unmarked_diagnostics useless_cpp_parens vulnerable_makefile_CVE-2009-4029 trailing_blank vulnerable_makefile_CVE-2012-3386 GEN sc_bracket_spacing_check ../configure.ac:35:AM_CONDITIONAL([EXECUTE_TESTS], [test "x$HAVE_PYTEST" == "xyes" -a "x$HAVE_REQUESTS" = "xyes"]) maint.mk: use "test C1 && test C2", not "test C1 -a C2"; use "test C1 || test C2", not "test C1 -o C2" gmake: *** [../maint.mk:1002: sc_prohibit_test_minus_ao] Error 1 gmake: *** Waiting for unfinished jobs.... Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: osinfo-db-tools-syntax-check » libvirt-fedora-28 #19
by ci＠centos.org 16 Apr '19

16 Apr '19

See <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-fedo…> ------------------------------------------ Started by upstream project "osinfo-db-tools-syntax-check" build number 19 originally caused by: Started by upstream project "osinfo-db-tools-build" build number 20 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-28 (libvirt) in workspace <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-fedo…> [osinfo-db-tools] $ /bin/sh -xe /tmp/jenkins455029706904390201.sh + cd build + /usr/bin/gmake syntax-check GFDL_version TAB_in_indentation Wundef_boolean avoid_attribute_unused_in_header avoid_if_before_free bindtextdomain bracket_spacing_check cast_of_argument_to_free cast_of_x_alloc_return_value changelog const_long_option copyright_format copyright_check error_message_period error_message_warn_fatal m4_quote_check makefile_TAB_only_indentation makefile_at_at_check makefile_path_separator_check obsolete_symbols po_check preprocessor_indentation prohibit_HAVE_MBRTOWC prohibit_S_IS_definition prohibit_always-defined_macros prohibit_argmatch_without_use prohibit_assert_without_use prohibit_atoi_atof prohibit_backup_files prohibit_c_ctype_without_use prohibit_canonicalize_without_use prohibit_cloexec_without_use prohibit_close_stream_without_use prohibit_cvs_keyword prohibit_defined_have_decl_tests prohibit_dirent_without_use prohibit_doubled_word prohibit_empty_lines_at_EOF prohibit_error_without_use prohibit_getopt_without_use prohibit_hash_pjw_without_use prohibit_hash_without_use prohibit_have_config_h prohibit_ignore_value_without_use prohibit_intprops_without_use prohibit_inttostr_without_use prohibit_magic_number_exit prohibit_long_options_without_use prohibit_openat_without_use prohibit_path_max_allocation prohibit_posixver_without_use prohibit_quote_without_use prohibit_quotearg_without_use prohibit_reversed_compare_failure prohibit_root_dev_ino_without_use prohibit_safe_read_without_use prohibit_same_without_use prohibit_signal_without_use prohibit_stat_st_blocks prohibit_stddef_without_use prohibit_stdio--_without_use prohibit_stdio-safer_without_use prohibit_strcmp prohibit_strings_without_use prohibit_strncpy prohibit_test_double_equal prohibit_test_minus_ao prohibit_undesirable_word_seq prohibit_verify_without_use prohibit_xalloc_without_use prohibit_xfreopen_without_use proper_name_utf8_requires_ICONV redundant_const require_config_h require_config_h_first require_test_exit_idiom space_tab texinfo_acronym tight_scope trailing_blank unmarked_diagnostics vulnerable_makefile_CVE-2009-4029 useless_cpp_parens vulnerable_makefile_CVE-2012-3386 GEN sc_bracket_spacing_check ../configure.ac:35:AM_CONDITIONAL([EXECUTE_TESTS], [test "x$HAVE_PYTEST" == "xyes" -a "x$HAVE_REQUESTS" = "xyes"]) maint.mk: use "test C1 && test C2", not "test C1 -a C2"; use "test C1 || test C2", not "test C1 -o C2" gmake: *** [../maint.mk:1002: sc_prohibit_test_minus_ao] Error 1 gmake: *** Waiting for unfinished jobs.... Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: osinfo-db-tools-syntax-check » libvirt-centos-7 #19
by ci＠centos.org 16 Apr '19

16 Apr '19

See <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-cent…> ------------------------------------------ Started by upstream project "osinfo-db-tools-syntax-check" build number 19 originally caused by: Started by upstream project "osinfo-db-tools-build" build number 20 originally caused by: 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/osinfo-db-tools-syntax-check/systems=libvirt-cent…> [osinfo-db-tools] $ /bin/sh -xe /tmp/jenkins4189265553176754481.sh + cd build + /usr/bin/gmake syntax-check GFDL_version TAB_in_indentation Wundef_boolean avoid_attribute_unused_in_header avoid_if_before_free bindtextdomain bracket_spacing_check cast_of_argument_to_free cast_of_x_alloc_return_value changelog const_long_option copyright_check copyright_format error_message_warn_fatal error_message_period m4_quote_check makefile_TAB_only_indentation makefile_at_at_check makefile_path_separator_check obsolete_symbols po_check preprocessor_indentation prohibit_HAVE_MBRTOWC prohibit_S_IS_definition prohibit_always-defined_macros prohibit_argmatch_without_use prohibit_assert_without_use prohibit_atoi_atof prohibit_c_ctype_without_use prohibit_backup_files prohibit_canonicalize_without_use prohibit_cloexec_without_use prohibit_close_stream_without_use prohibit_cvs_keyword prohibit_defined_have_decl_tests prohibit_dirent_without_use prohibit_doubled_word prohibit_empty_lines_at_EOF prohibit_error_without_use prohibit_getopt_without_use prohibit_hash_pjw_without_use prohibit_hash_without_use prohibit_ignore_value_without_use prohibit_intprops_without_use prohibit_inttostr_without_use prohibit_have_config_h prohibit_long_options_without_use prohibit_magic_number_exit prohibit_openat_without_use prohibit_path_max_allocation prohibit_posixver_without_use prohibit_quote_without_use prohibit_quotearg_without_use prohibit_reversed_compare_failure prohibit_root_dev_ino_without_use prohibit_safe_read_without_use prohibit_same_without_use prohibit_signal_without_use prohibit_stddef_without_use prohibit_stat_st_blocks prohibit_stdio--_without_use prohibit_stdio-safer_without_use prohibit_strings_without_use prohibit_strncpy prohibit_strcmp prohibit_test_double_equal prohibit_test_minus_ao prohibit_undesirable_word_seq prohibit_verify_without_use prohibit_xalloc_without_use prohibit_xfreopen_without_use proper_name_utf8_requires_ICONV redundant_const require_config_h require_config_h_first require_test_exit_idiom space_tab texinfo_acronym tight_scope trailing_blank unmarked_diagnostics useless_cpp_parens vulnerable_makefile_CVE-2009-4029 vulnerable_makefile_CVE-2012-3386 GEN sc_bracket_spacing_check maint.mk: skipping test sc_preprocessor_indentation: cppi not installed ../configure.ac:35:AM_CONDITIONAL([EXECUTE_TESTS], [test "x$HAVE_PYTEST" == "xyes" -a "x$HAVE_REQUESTS" = "xyes"]) maint.mk: use "test C1 && test C2", not "test C1 -a C2"; use "test C1 || test C2", not "test C1 -o C2" gmake: *** [sc_prohibit_test_minus_ao] Error 1 gmake: *** Waiting for unfinished jobs.... Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: osinfo-db-tools-syntax-check » libvirt-debian-9 #19
by ci＠centos.org 16 Apr '19

16 Apr '19

See <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-debi…> ------------------------------------------ Started by upstream project "osinfo-db-tools-syntax-check" build number 19 originally caused by: Started by upstream project "osinfo-db-tools-build" build number 20 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-9 (libvirt) in workspace <https://ci.centos.org/job/osinfo-db-tools-syntax-check/systems=libvirt-debi…> [osinfo-db-tools] $ /bin/sh -xe /tmp/jenkins7356329139607702681.sh + cd build + /usr/bin/make syntax-check GFDL_version TAB_in_indentation Wundef_boolean avoid_attribute_unused_in_header avoid_if_before_free bindtextdomain bracket_spacing_check cast_of_argument_to_free cast_of_x_alloc_return_value changelog const_long_option copyright_check copyright_format error_message_period error_message_warn_fatal m4_quote_check makefile_TAB_only_indentation makefile_at_at_check makefile_path_separator_check obsolete_symbols po_check preprocessor_indentation prohibit_HAVE_MBRTOWC prohibit_S_IS_definition prohibit_always-defined_macros prohibit_argmatch_without_use prohibit_assert_without_use prohibit_atoi_atof prohibit_backup_files prohibit_c_ctype_without_use prohibit_canonicalize_without_use prohibit_cloexec_without_use prohibit_close_stream_without_use prohibit_cvs_keyword prohibit_dirent_without_use prohibit_defined_have_decl_tests prohibit_doubled_word prohibit_empty_lines_at_EOF prohibit_error_without_use prohibit_getopt_without_use prohibit_hash_pjw_without_use prohibit_hash_without_use prohibit_have_config_h prohibit_ignore_value_without_use prohibit_intprops_without_use prohibit_inttostr_without_use prohibit_long_options_without_use prohibit_magic_number_exit prohibit_path_max_allocation prohibit_openat_without_use prohibit_posixver_without_use prohibit_quotearg_without_use prohibit_quote_without_use prohibit_reversed_compare_failure prohibit_root_dev_ino_without_use prohibit_safe_read_without_use prohibit_same_without_use prohibit_signal_without_use prohibit_stat_st_blocks prohibit_stddef_without_use prohibit_stdio--_without_use prohibit_stdio-safer_without_use prohibit_strcmp prohibit_strings_without_use prohibit_test_double_equal prohibit_strncpy prohibit_undesirable_word_seq prohibit_test_minus_ao prohibit_verify_without_use prohibit_xalloc_without_use prohibit_xfreopen_without_use proper_name_utf8_requires_ICONV redundant_const require_config_h require_test_exit_idiom require_config_h_first space_tab texinfo_acronym tight_scope trailing_blank unmarked_diagnostics useless_cpp_parens vulnerable_makefile_CVE-2009-4029 vulnerable_makefile_CVE-2012-3386 GEN sc_bracket_spacing_check maint.mk: skipping test sc_preprocessor_indentation: cppi not installed ../configure.ac:35:AM_CONDITIONAL([EXECUTE_TESTS], [test "x$HAVE_PYTEST" == "xyes" -a "x$HAVE_REQUESTS" = "xyes"]) maint.mk: use "test C1 && test C2", not "test C1 -a C2"; use "test C1 || test C2", not "test C1 -o C2" ../maint.mk:1002: recipe for target 'sc_prohibit_test_minus_ao' failed make: *** [sc_prohibit_test_minus_ao] Error 1 make: *** Waiting for unfinished jobs.... Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Broken: libvirt/libvirt#2249 (master - 545b057)
by Travis CI 16 Apr '19

16 Apr '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2249 Status: Broken Duration: 22 mins and 27 secs Commit: 545b057 (master) Author: Martin Kletzander Message: docs: Add emulatorsched support to news.xml Signed-off-by: Martin Kletzander <mkletzan(a)redhat.com> Reviewed-by: Ján Tomko <jtomko(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/ad32d7616577...545b0574fd27 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/520735089?utm_medium=notificat… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

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

16 Apr '19

See <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…> ------------------------------------------ Started by upstream project "libvirt-dbus-check" build number 308 originally caused by: Started by upstream project "libvirt-dbus-syntax-check" build number 351 originally caused by: Started by upstream project "libvirt-dbus-build" build number 358 originally caused by: Started by upstream project "libvirt-glib-build" build number 355 originally caused by: Started by upstream project "libvirt-build" build number 453 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-dbus-check/systems=libvirt-fedora-rawhide…> [libvirt-dbus] $ /bin/sh -xe /tmp/jenkins878545359634288684.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-rawhide…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> Making check in docs gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> Making check in src gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> Making check in tests gmake[1]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> /usr/bin/gmake test_util gmake[2]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> CC test_util-test_util.o CCLD test_util gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> /usr/bin/gmake check-TESTS gmake[2]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> gmake[3]: Entering directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> 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-rawhide…'> gmake[2]: *** [Makefile:874: check-TESTS] Error 2 gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> gmake[1]: *** [Makefile:990: check-am] Error 2 gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…'> 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.3, pytest-4.3.1, py-1.7.0, pluggy-0.8.1 rootdir: <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-fedora-rawhide…,> inifile: collected 35 items ../../tests/test_connect.py .........................F......... [100%] =================================== FAILURES =================================== _______________ TestConnect.test_connect_node_device_create_xml ________________ Fixture "node_device_create" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-direct… about how to update your code. ===================== 1 failed, 34 passed in 25.81 seconds ===================== FAIL test_connect.py (exit status: 1) + exit 1 Build step 'Execute shell' marked build as failure

1 28

[Libvirt-ci] Build failed in Jenkins: libvirt-dbus-check » libvirt-freebsd-11 #290
by ci＠centos.org 16 Apr '19

16 Apr '19

See <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/290…> ------------------------------------------ Started by upstream project "libvirt-dbus-check" build number 290 originally caused by: Started by upstream project "libvirt-dbus-syntax-check" build number 333 originally caused by: Started by upstream project "libvirt-dbus-build" build number 340 originally caused by: Started by upstream project "libvirt-glib-build" build number 337 originally caused by: Started by upstream project "libvirt-build" build number 435 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-freebsd-11 (libvirt) in workspace <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/> [libvirt-dbus] $ /bin/sh -xe /tmp/jenkins4534165812246974153.sh + cd build + /usr/local/bin/gmake check Making check in data gmake[1]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> Making check in docs gmake[1]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> Making check in src gmake[1]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> Making check in tests gmake[1]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> /usr/local/bin/gmake test_util gmake[2]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> CC test_util-test_util.o CCLD test_util gmake[2]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> /usr/local/bin/gmake check-TESTS gmake[2]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> gmake[3]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> 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 '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> gmake[2]: *** [Makefile:874: check-TESTS] Error 2 gmake[2]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> gmake[1]: *** [Makefile:990: check-am] Error 2 gmake[1]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/…'> 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 freebsd11 -- Python 3.6.8, pytest-4.3.1, py-1.8.0, pluggy-0.7.1 rootdir: /usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-11/ws/,> inifile: collected 35 items ../../tests/test_connect.py .........................F......... [100%] =================================== FAILURES =================================== _______________ TestConnect.test_connect_node_device_create_xml ________________ Fixture "node_device_create" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-direct… about how to update your code. ===================== 1 failed, 34 passed in 15.02 seconds ===================== FAIL test_connect.py (exit status: 1) + exit 1 Build step 'Execute shell' marked build as failure

1 46

[Libvirt-ci] Build failed in Jenkins: libvirt-dbus-check » libvirt-freebsd-12 #290
by ci＠centos.org 16 Apr '19

16 Apr '19

See <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/290…> ------------------------------------------ Started by upstream project "libvirt-dbus-check" build number 290 originally caused by: Started by upstream project "libvirt-dbus-syntax-check" build number 333 originally caused by: Started by upstream project "libvirt-dbus-build" build number 340 originally caused by: Started by upstream project "libvirt-glib-build" build number 337 originally caused by: Started by upstream project "libvirt-build" build number 435 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-freebsd-12 (libvirt) in workspace <https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/> [libvirt-dbus] $ /bin/sh -xe /tmp/jenkins4439176497064658175.sh + cd build + /usr/local/bin/gmake check Making check in data gmake[1]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> Making check in docs gmake[1]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> Making check in src gmake[1]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> Making check in tests gmake[1]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> /usr/local/bin/gmake test_util gmake[2]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> CC test_util-test_util.o CCLD test_util gmake[2]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> /usr/local/bin/gmake check-TESTS gmake[2]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> gmake[3]: Entering directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> 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 '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> gmake[2]: *** [Makefile:874: check-TESTS] Error 2 gmake[2]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> gmake[1]: *** [Makefile:990: check-am] Error 2 gmake[1]: Leaving directory '/usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/…'> 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 freebsd12 -- Python 3.6.8, pytest-4.3.1, py-1.8.0, pluggy-0.7.1 rootdir: /usr<https://ci.centos.org/job/libvirt-dbus-check/systems=libvirt-freebsd-12/ws/,> inifile: collected 35 items ../../tests/test_connect.py .........................F......... [100%] =================================== FAILURES =================================== _______________ TestConnect.test_connect_node_device_create_xml ________________ Fixture "node_device_create" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-direct… about how to update your code. ===================== 1 failed, 34 passed in 13.80 seconds ===================== FAIL test_connect.py (exit status: 1) + exit 1 Build step 'Execute shell' marked build as failure

1 46

[Libvirt-ci] Build failed in Jenkins: libvirt-glib-build » libvirt-freebsd-12 #379
by ci＠centos.org 15 Apr '19

15 Apr '19

See <https://ci.centos.org/job/libvirt-glib-build/systems=libvirt-freebsd-12/379…> ------------------------------------------ Started by upstream project "libvirt-glib-build" build number 379 originally caused by: Started by upstream project "libvirt-build" build number 477 originally caused by: 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-freebsd-12 (libvirt) in workspace <https://ci.centos.org/job/libvirt-glib-build/systems=libvirt-freebsd-12/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/libvirt/libvirt-glib.git # timeout=10 Fetching upstream changes from https://github.com/libvirt/libvirt-glib.git > git --version # timeout=10 > git fetch --tags --force --progress https://github.com/libvirt/libvirt-glib.git +refs/heads/*:refs/remotes/origin/* Checking out Revision f3d93271c6c535b5d4014b2ebccd127f32311b88 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f f3d93271c6c535b5d4014b2ebccd127f32311b88 Commit message: "po: refresh translations from zanata" > git rev-list --no-walk f3d93271c6c535b5d4014b2ebccd127f32311b88 # timeout=10 FATAL: Invalid id: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from n64.gusty.ci.centos.org/172.19.2.192:33669 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) at com.sun.proxy.$Proxy85.isCommitInRepo(Unknown Source) at org.jenkinsci.plugins.gitclient.RemoteGitImpl.isCommitInRepo(RemoteGitImpl.java:285) at hudson.plugins.git.GitSCM.computeChangeLog(GitSCM.java:1340) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1264) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1810) at hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) org.eclipse.jgit.errors.InvalidObjectIdException: Invalid id: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:232) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$10.execute(CliGitAPIImpl.java:2559) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.isCommitInRepo(CliGitAPIImpl.java:2610) at hudson.plugins.git.GitAPI.isCommitInRepo(GitAPI.java:237) at sun.reflect.GeneratedMethodAccessor428.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748)

1 1

[Libvirt-ci] Build failed in Jenkins: libvirt+mingw64-build » libvirt-fedora-rawhide #506
by ci＠centos.org 15 Apr '19

15 Apr '19

See <https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…> Changes: [jdenemar] cputest: Add data for Intel(R) Xeon(R) Platinum 8268 CPU [jdenemar] cpu_map: Add Cascadelake-Server CPU model [jdenemar] cpu_x86: Introduce virCPUx86DataItem container struct [jdenemar] cpu_x86: Rename virCPUx86Vendor.cpuid [jdenemar] cpu_x86: Rename virCPUx86DataItem variables [jdenemar] cpu_x86: Rename x86DataCpuidNext function [jdenemar] cpu_x86: Rename x86DataCpuid [jdenemar] cpu_x86: Rename virCPUx86CPUIDSorter [jdenemar] cpu_x86: Rename virCPUx86DataAddCPUIDInt [jdenemar] cpu_x86: Rename virCPUx86DataAddCPUID [jdenemar] cpu_x86: Rename virCPUx86VendorToCPUID [jdenemar] cpu_x86: Simplify x86DataAdd [jdenemar] cpu_x86: Introduce virCPUx86DataCmp [jdenemar] cpu_x86: Make x86cpuidSetBits more general [jdenemar] cpu_x86: Make x86cpuidClearBits more general [jdenemar] cpu_x86: Make x86cpuidAndBits more general [jdenemar] cpu_x86: Make x86cpuidMatchMasked more general [jdenemar] cpu_x86: Make x86cpuidMatch more general [jdenemar] cpu_x86: Store virCPUx86DataItem content in union [jdenemar] cpu_x86: Add support for storing MSR features in CPU map [jdenemar] cpu_x86: Move *CheckFeature functions [jdenemar] cputest: Drop support for old QEMU from cpu-parse.sh [jdenemar] cputest: Generalize function names in cpu-cpuid.py [jdenemar] cputest: Fix comparison in checkCPUIDFeature in cpu-cpuid.py [jdenemar] cputest: Rename in_e[ac]x as e[ac]x_in in cpu-cpuid.py [jdenemar] cputest: Prepare cpu-cpuid.py for MSR features [jdenemar] cputest: Generalize feature parsing in cpu-cpuid.py [jdenemar] cputest: Add support for MSR features to cpu-gather.sh [jdenemar] cputest: Add support for MSR features to cpu-parse.sh [jdenemar] cputest: Add support for MSR features to cpu-cpuid.py [jdenemar] vircpuhost: Add support for reading MSRs ------------------------------------------ [...truncated 127.66 KB...] CC pipe.lo CC poll.lo CC posix_openpt.lo ../../../gnulib/lib/poll.c: In function 'poll': ../../../gnulib/lib/poll.c:519:39: warning: passing argument 5 of 'select' from incompatible pointer type [-Wincompatible-pointer-types] if (select (0, &rfds, &wfds, &xfds, &tv0) > 0) ^~~~ In file included from ../../../gnulib/lib/poll.c:39: /usr/x86_64-w64-mingw32/sys-root/mingw/include/winsock2.h:995:116: note: expected 'PTIMEVAL' {aka 'struct timeval * const'} but argument is of type 'struct rpl_timeval *' WINSOCK_API_LINKAGE int WSAAPI select(int nfds,fd_set *readfds,fd_set *writefds,fd_set *exceptfds,const PTIMEVAL timeout); ~~~~~~~~~~~~~~~^~~~~~~ ../../../gnulib/lib/poll.c:555:37: warning: passing argument 5 of 'select' from incompatible pointer type [-Wincompatible-pointer-types] select (0, &rfds, &wfds, &xfds, &tv0); ^~~~ In file included from ../../../gnulib/lib/poll.c:39: /usr/x86_64-w64-mingw32/sys-root/mingw/include/winsock2.h:995:116: note: expected 'PTIMEVAL' {aka 'struct timeval * const'} but argument is of type 'struct rpl_timeval *' WINSOCK_API_LINKAGE int WSAAPI select(int nfds,fd_set *readfds,fd_set *writefds,fd_set *exceptfds,const PTIMEVAL timeout); ~~~~~~~~~~~~~~~^~~~~~~ CC printf-args.lo CC printf-parse.lo CC pthread_sigmask.lo CC raise.lo CC rawmemchr.lo CC readlink.lo CC realloc.lo CC recv.lo CC regex.lo CC secure_getenv.lo CC select.lo CC send.lo CC setenv.lo CC setsockopt.lo CC sigaction.lo CC sigprocmask.lo CC sleep.lo CC snprintf.lo CC socket.lo CC stat.lo CC stat-w32.lo CC stdio-read.lo CC stdio-write.lo CC stpcpy.lo CC strchrnul.lo CC strdup.lo CC strerror.lo CC strerror-override.lo CC strerror_r.lo CC strndup.lo CC strptime.lo CC strsep.lo CC time_r.lo CC timegm.lo CC ttyname_r.lo CC uname.lo CC unsetenv.lo CC usleep.lo CC vasnprintf.lo CC vsnprintf.lo CC waitpid.lo CC wcwidth.lo CC glthread/lock.lo CC uniwidth/width.lo CCLD libgnu.la gmake[3]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> Making all in include/libvirt gmake[2]: Entering directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> gmake[2]: Nothing to be done for 'all'. gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> Making all in src gmake[2]: Entering directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> GEN util/virkeycodetable_linux.h GEN util/virkeycodetable_osx.h GEN util/virkeycodetable_atset1.h GEN util/virkeycodetable_atset2.h GEN util/virkeycodetable_xtkbd.h GEN util/virkeycodetable_atset3.h GEN util/virkeycodetable_usb.h GEN util/virkeycodetable_win32.h GEN util/virkeycodetable_qnum.h GEN util/virkeynametable_linux.h GEN util/virkeynametable_osx.h GEN util/virkeynametable_win32.h GEN ../../src/access/org.libvirt.api.policy GEN access/viraccessapicheck.h GEN access/viraccessapicheck.c GEN access/viraccessapicheckqemu.h GEN access/viraccessapicheckqemu.c GEN access/viraccessapichecklxc.h GEN access/viraccessapichecklxc.c GEN libvirt_access.xml GEN libvirt_access_qemu.xml GEN libvirt_access_lxc.xml GEN logging/log_protocol.h GEN logging/log_daemon_dispatch_stubs.h GEN locking/lock_protocol.h GEN locking/lock_daemon_dispatch_stubs.h GEN admin/admin_protocol.h GEN admin/admin_client.h GEN admin/admin_server_dispatch_stubs.h GEN rpc/virnetprotocol.h GEN rpc/virkeepaliveprotocol.h GEN .esx_vi_generator.stamp GEN .hyperv_wmi_generator.stamp GEN lxc/lxc_monitor_protocol.h GEN lxc/lxc_monitor_dispatch.h GEN ../../src/hyperv/hyperv_wmi_classes.generated.typedef GEN ../../src/hyperv/hyperv_wmi_classes.generated.h GEN ../../src/hyperv/hyperv_wmi_classes.generated.c GEN lxc/lxc_controller_dispatch.h GEN ../../src/esx/esx_vi_types.generated.typedef GEN ../../src/esx/esx_vi_types.generated.typeenum GEN ../../src/esx/esx_vi_types.generated.typetostring GEN ../../src/esx/esx_vi_types.generated.typefromstring GEN ../../src/esx/esx_vi_types.generated.h GEN ../../src/esx/esx_vi_types.generated.c GEN ../../src/esx/esx_vi_methods.generated.h GEN ../../src/esx/esx_vi_methods.generated.c GEN ../../src/esx/esx_vi_methods.generated.macro GEN ../../src/esx/esx_vi.generated.h GEN ../../src/esx/esx_vi.generated.c GEN remote/remote_protocol.h GEN remote/remote_client_bodies.h GEN remote/lxc_protocol.h GEN remote/lxc_client_bodies.h GEN remote/qemu_protocol.h GEN remote/qemu_client_bodies.h GEN remote/remote_daemon_dispatch_stubs.h GEN remote/remote_daemon_dispatch_lxc_stubs.h GEN remote/remote_daemon_dispatch_qemu_stubs.h GEN libvirt_access.syms GEN libvirt_access_qemu.syms GEN libvirt_access_lxc.syms GEN libvirt_qemu.def GEN libvirt_lxc.def GEN libvirt_admin.syms GEN libvirtd.qemu.logrotate GEN libvirtd.lxc.logrotate GEN libvirtd.libxl.logrotate GEN libvirtd.logrotate GEN logging/log_protocol.c GEN locking/lock_protocol.c GEN admin/admin_protocol.c GEN rpc/virnetprotocol.c GEN rpc/virkeepaliveprotocol.c GEN lxc/lxc_monitor_protocol.c GEN remote/remote_protocol.c GEN remote/lxc_protocol.c GEN remote/qemu_protocol.c GEN libvirt.syms GEN libvirt_admin.def GEN libvirt.def /usr/bin/gmake all-am gmake[3]: Entering directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> CC libvirt_driver_la-driver.lo CC libvirt_driver_la-datatypes.lo CC libvirt_driver_la-libvirt.lo CC libvirt_driver_la-libvirt-domain.lo CC libvirt_driver_la-libvirt-domain-snapshot.lo CC libvirt_driver_la-libvirt-host.lo CC libvirt_driver_la-libvirt-interface.lo CC libvirt_driver_la-libvirt-nodedev.lo CC libvirt_driver_la-libvirt-network.lo CC libvirt_driver_la-libvirt-nwfilter.lo CC libvirt_driver_la-libvirt-secret.lo CC libvirt_driver_la-libvirt-storage.lo CC libvirt_driver_la-libvirt-stream.lo CC libvirt_qemu_la-libvirt-qemu.lo CC libvirt_lxc_la-libvirt-lxc.lo CC libvirt_admin_la-libvirt-admin.lo CC libvirt_admin_la-datatypes.lo CC admin/libvirt_driver_admin_la-admin_protocol.lo CC admin/libvirt_driver_admin_la-admin_server.lo CC admin/libvirt_driver_admin_la-admin_server_dispatch.lo GEN util/virkeycode-linux.pod GEN util/virkeycode-osx.pod GEN util/virkeycode-atset1.pod GEN util/virkeycode-atset2.pod GEN util/virkeycode-atset3.pod GEN util/virkeycode-xtkbd.pod GEN util/virkeycode-usb.pod GEN util/virkeycode-win32.pod GEN util/virkeycode-qnum.pod GEN util/virkeyname-linux.pod GEN util/virkeyname-osx.pod GEN util/virkeyname-win32.pod CC util/libvirt_util_la-viralloc.lo CC util/libvirt_util_la-virarch.lo CC util/libvirt_util_la-virarptable.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-virbitmap.lo CC util/libvirt_util_la-virbuffer.lo CC util/libvirt_util_la-virperf.lo CC util/libvirt_util_la-vircgroup.lo CC util/libvirt_util_la-vircgroupbackend.lo CC util/libvirt_util_la-vircgroupv1.lo CC util/libvirt_util_la-vircgroupv2.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-virdevmapper.lo CC util/libvirt_util_la-virdnsmasq.lo CC util/libvirt_util_la-virebtables.lo CC util/libvirt_util_la-virenum.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-virfcp.lo CC util/libvirt_util_la-virfdstream.lo CC util/libvirt_util_la-virfile.lo CC util/libvirt_util_la-virfirewall.lo CC util/libvirt_util_la-virfirewalld.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 ../../src/util/virhostcpu.c: In function 'virHostCPUGetMSR': ../../src/util/virhostcpu.c:1319:18: error: implicit declaration of function 'pread'; did you mean 'fread'? [-Werror=implicit-function-declaration] int rc = pread(fd, msr, sizeof(*msr), index); ^~~~~ fread ../../src/util/virhostcpu.c:1319:18: error: nested extern declaration of 'pread' [-Werror=nested-externs] cc1: all warnings being treated as errors gmake[3]: *** [Makefile:11962: util/libvirt_util_la-virhostcpu.lo] Error 1 gmake[3]: *** Waiting for unfinished jobs.... rm util/virkeyname-osx.pod util/virkeycode-xtkbd.pod util/virkeycode-atset3.pod util/virkeycode-usb.pod util/virkeycode-qnum.pod util/virkeycode-win32.pod util/virkeyname-linux.pod util/virkeycode-osx.pod util/virkeycode-linux.pod util/virkeycode-atset1.pod util/virkeyname-win32.pod util/virkeycode-atset2.pod gmake[3]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> gmake[2]: *** [Makefile:7127: all] Error 2 gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> gmake[1]: *** [Makefile:2257: all-recursive] Error 1 gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> gmake: *** [Makefile:2149: all] Error 2 Build step 'Execute shell' marked build as failure

1 4

[Libvirt-ci] Build failed in Jenkins: libvirt+mingw32-build » libvirt-fedora-rawhide #506
by ci＠centos.org 15 Apr '19

15 Apr '19

See <https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…> Changes: [jdenemar] cputest: Add data for Intel(R) Xeon(R) Platinum 8268 CPU [jdenemar] cpu_map: Add Cascadelake-Server CPU model [jdenemar] cpu_x86: Introduce virCPUx86DataItem container struct [jdenemar] cpu_x86: Rename virCPUx86Vendor.cpuid [jdenemar] cpu_x86: Rename virCPUx86DataItem variables [jdenemar] cpu_x86: Rename x86DataCpuidNext function [jdenemar] cpu_x86: Rename x86DataCpuid [jdenemar] cpu_x86: Rename virCPUx86CPUIDSorter [jdenemar] cpu_x86: Rename virCPUx86DataAddCPUIDInt [jdenemar] cpu_x86: Rename virCPUx86DataAddCPUID [jdenemar] cpu_x86: Rename virCPUx86VendorToCPUID [jdenemar] cpu_x86: Simplify x86DataAdd [jdenemar] cpu_x86: Introduce virCPUx86DataCmp [jdenemar] cpu_x86: Make x86cpuidSetBits more general [jdenemar] cpu_x86: Make x86cpuidClearBits more general [jdenemar] cpu_x86: Make x86cpuidAndBits more general [jdenemar] cpu_x86: Make x86cpuidMatchMasked more general [jdenemar] cpu_x86: Make x86cpuidMatch more general [jdenemar] cpu_x86: Store virCPUx86DataItem content in union [jdenemar] cpu_x86: Add support for storing MSR features in CPU map [jdenemar] cpu_x86: Move *CheckFeature functions [jdenemar] cputest: Drop support for old QEMU from cpu-parse.sh [jdenemar] cputest: Generalize function names in cpu-cpuid.py [jdenemar] cputest: Fix comparison in checkCPUIDFeature in cpu-cpuid.py [jdenemar] cputest: Rename in_e[ac]x as e[ac]x_in in cpu-cpuid.py [jdenemar] cputest: Prepare cpu-cpuid.py for MSR features [jdenemar] cputest: Generalize feature parsing in cpu-cpuid.py [jdenemar] cputest: Add support for MSR features to cpu-gather.sh [jdenemar] cputest: Add support for MSR features to cpu-parse.sh [jdenemar] cputest: Add support for MSR features to cpu-cpuid.py [jdenemar] vircpuhost: Add support for reading MSRs ------------------------------------------ [...truncated 127.05 KB...] CC localtime-buffer.lo CC lseek.lo CC malloc.lo CC mbrtowc.lo CC mbsinit.lo CC mbsrtowcs.lo CC mbsrtowcs-state.lo CC mkdir.lo CC mkdtemp.lo CC mkostemp.lo CC mkostemps.lo CC mktime.lo CC msvc-inval.lo CC msvc-nothrow.lo CC nl_langinfo.lo CC open.lo CC openpty.lo CC perror.lo CC pipe.lo CC poll.lo CC posix_openpt.lo CC printf-args.lo CC printf-parse.lo CC pthread_sigmask.lo CC raise.lo CC rawmemchr.lo CC readlink.lo CC realloc.lo CC recv.lo CC regex.lo CC secure_getenv.lo CC select.lo CC send.lo CC setenv.lo CC setsockopt.lo CC sigaction.lo CC sigprocmask.lo CC sleep.lo CC snprintf.lo CC socket.lo CC stat.lo CC stat-w32.lo CC stdio-read.lo CC stdio-write.lo CC stpcpy.lo CC strchrnul.lo CC strdup.lo CC strerror.lo CC strerror-override.lo CC strerror_r.lo CC strndup.lo CC strptime.lo CC strsep.lo CC time_r.lo CC timegm.lo CC ttyname_r.lo CC uname.lo CC unsetenv.lo CC usleep.lo CC vasnprintf.lo CC vsnprintf.lo CC waitpid.lo CC wcwidth.lo CC glthread/lock.lo CC uniwidth/width.lo CCLD libgnu.la gmake[3]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> Making all in include/libvirt gmake[2]: Entering directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> gmake[2]: Nothing to be done for 'all'. gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> Making all in src gmake[2]: Entering directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> GEN util/virkeycodetable_linux.h GEN util/virkeycodetable_osx.h GEN util/virkeycodetable_atset1.h GEN util/virkeycodetable_atset2.h GEN util/virkeycodetable_atset3.h GEN util/virkeycodetable_xtkbd.h GEN util/virkeycodetable_usb.h GEN util/virkeycodetable_win32.h GEN util/virkeycodetable_qnum.h GEN util/virkeynametable_linux.h GEN util/virkeynametable_osx.h GEN util/virkeynametable_win32.h GEN ../../src/access/org.libvirt.api.policy GEN access/viraccessapicheck.h GEN access/viraccessapicheck.c GEN access/viraccessapicheckqemu.h GEN access/viraccessapicheckqemu.c GEN access/viraccessapichecklxc.h GEN access/viraccessapichecklxc.c GEN libvirt_access.xml GEN libvirt_access_qemu.xml GEN libvirt_access_lxc.xml GEN logging/log_protocol.h GEN logging/log_daemon_dispatch_stubs.h GEN locking/lock_protocol.h GEN locking/lock_daemon_dispatch_stubs.h GEN admin/admin_protocol.h GEN admin/admin_client.h GEN admin/admin_server_dispatch_stubs.h GEN rpc/virnetprotocol.h GEN rpc/virkeepaliveprotocol.h GEN .esx_vi_generator.stamp GEN .hyperv_wmi_generator.stamp GEN lxc/lxc_monitor_protocol.h GEN ../../src/hyperv/hyperv_wmi_classes.generated.typedef GEN ../../src/hyperv/hyperv_wmi_classes.generated.h GEN ../../src/hyperv/hyperv_wmi_classes.generated.c GEN lxc/lxc_monitor_dispatch.h GEN lxc/lxc_controller_dispatch.h GEN ../../src/esx/esx_vi_types.generated.typedef GEN ../../src/esx/esx_vi_types.generated.typeenum GEN ../../src/esx/esx_vi_types.generated.typetostring GEN ../../src/esx/esx_vi_types.generated.typefromstring GEN ../../src/esx/esx_vi_types.generated.h GEN ../../src/esx/esx_vi_types.generated.c GEN ../../src/esx/esx_vi_methods.generated.h GEN ../../src/esx/esx_vi_methods.generated.c GEN ../../src/esx/esx_vi_methods.generated.macro GEN ../../src/esx/esx_vi.generated.h GEN ../../src/esx/esx_vi.generated.c GEN remote/remote_protocol.h GEN remote/remote_client_bodies.h GEN remote/lxc_protocol.h GEN remote/lxc_client_bodies.h GEN remote/qemu_protocol.h GEN remote/qemu_client_bodies.h GEN remote/remote_daemon_dispatch_stubs.h GEN remote/remote_daemon_dispatch_lxc_stubs.h GEN remote/remote_daemon_dispatch_qemu_stubs.h GEN libvirt_access.syms GEN libvirt_access_qemu.syms GEN libvirt_access_lxc.syms GEN libvirt_qemu.def GEN libvirt_lxc.def GEN libvirt_admin.syms GEN libvirtd.qemu.logrotate GEN libvirtd.lxc.logrotate GEN libvirtd.libxl.logrotate GEN libvirtd.logrotate GEN logging/log_protocol.c GEN locking/lock_protocol.c GEN admin/admin_protocol.c GEN rpc/virnetprotocol.c GEN rpc/virkeepaliveprotocol.c GEN lxc/lxc_monitor_protocol.c GEN remote/remote_protocol.c GEN remote/lxc_protocol.c GEN remote/qemu_protocol.c GEN libvirt.syms GEN libvirt_admin.def GEN libvirt.def /usr/bin/gmake all-am gmake[3]: Entering directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> CC libvirt_driver_la-driver.lo CC libvirt_driver_la-libvirt.lo CC libvirt_driver_la-datatypes.lo CC libvirt_driver_la-libvirt-domain.lo CC libvirt_driver_la-libvirt-domain-snapshot.lo CC libvirt_driver_la-libvirt-host.lo CC libvirt_driver_la-libvirt-interface.lo CC libvirt_driver_la-libvirt-network.lo CC libvirt_driver_la-libvirt-nodedev.lo CC libvirt_driver_la-libvirt-nwfilter.lo CC libvirt_driver_la-libvirt-secret.lo CC libvirt_driver_la-libvirt-storage.lo CC libvirt_driver_la-libvirt-stream.lo CC libvirt_qemu_la-libvirt-qemu.lo CC libvirt_lxc_la-libvirt-lxc.lo CC libvirt_admin_la-libvirt-admin.lo CC libvirt_admin_la-datatypes.lo GEN util/virkeycode-linux.pod GEN util/virkeycode-osx.pod GEN util/virkeycode-atset1.pod GEN util/virkeycode-atset2.pod GEN util/virkeycode-atset3.pod GEN util/virkeycode-xtkbd.pod GEN util/virkeycode-usb.pod GEN util/virkeycode-win32.pod GEN util/virkeycode-qnum.pod GEN util/virkeyname-linux.pod GEN util/virkeyname-osx.pod GEN util/virkeyname-win32.pod CC util/libvirt_util_la-viralloc.lo CC util/libvirt_util_la-virarch.lo CC util/libvirt_util_la-virarptable.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-virbitmap.lo CC util/libvirt_util_la-virbuffer.lo CC util/libvirt_util_la-virperf.lo CC util/libvirt_util_la-vircgroup.lo CC util/libvirt_util_la-vircgroupbackend.lo CC util/libvirt_util_la-vircgroupv1.lo CC util/libvirt_util_la-vircgroupv2.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-virdevmapper.lo CC util/libvirt_util_la-virdnsmasq.lo CC util/libvirt_util_la-virebtables.lo CC util/libvirt_util_la-virenum.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-virfcp.lo CC util/libvirt_util_la-virfdstream.lo CC util/libvirt_util_la-virfile.lo CC util/libvirt_util_la-virfirewall.lo CC util/libvirt_util_la-virfirewalld.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 ../../src/util/virhostcpu.c: In function 'virHostCPUGetMSR': ../../src/util/virhostcpu.c:1319:18: error: implicit declaration of function 'pread'; did you mean 'fread'? [-Werror=implicit-function-declaration] int rc = pread(fd, msr, sizeof(*msr), index); ^~~~~ fread ../../src/util/virhostcpu.c:1319:18: error: nested extern declaration of 'pread' [-Werror=nested-externs] cc1: all warnings being treated as errors gmake[3]: *** [Makefile:11962: util/libvirt_util_la-virhostcpu.lo] Error 1 gmake[3]: *** Waiting for unfinished jobs.... rm util/virkeyname-osx.pod util/virkeycode-xtkbd.pod util/virkeycode-atset3.pod util/virkeycode-usb.pod util/virkeycode-qnum.pod util/virkeycode-win32.pod util/virkeyname-linux.pod util/virkeycode-osx.pod util/virkeycode-linux.pod util/virkeycode-atset1.pod util/virkeyname-win32.pod util/virkeycode-atset2.pod gmake[3]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> gmake[2]: *** [Makefile:7127: all] Error 2 gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> gmake[1]: *** [Makefile:2257: all-recursive] Error 1 gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> gmake: *** [Makefile:2149: all] Error 2 Build step 'Execute shell' marked build as failure

1 4

[Libvirt-ci] Fixed: libvirt/libvirt#2235 (master - 0a97486)
by Travis CI 15 Apr '19

15 Apr '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2235 Status: Fixed Duration: 25 mins and 53 secs Commit: 0a97486 (master) Author: Michal Privoznik Message: cpu_x86: Fix placement of *CheckFeature functions In e17d10386 these functions were mistakenly moved into an #ifdef block, but remained used outside of it leaving the build broken for platforms where #ifdef evaluated to false. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Reviewed-by: Jiri Denemark <jdenemar(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/1a922648f67f...0a97486e092c View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/520168804?utm_medium=notificat… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

[Libvirt-ci] Still Failing: libvirt/libvirt#2234 (master - 1a92264)
by Travis CI 15 Apr '19

15 Apr '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2234 Status: Still Failing Duration: 22 mins and 19 secs Commit: 1a92264 (master) Author: Daniel Henrique Barboza Message: PPC64 support for NVIDIA V100 GPU with NVLink2 passthrough The NVIDIA V100 GPU has an onboard RAM that is mapped into the host memory and accessible as normal RAM via an NVLink2 bridge. When passed through in a guest, QEMU puts the NVIDIA RAM window in a non-contiguous area, above the PCI MMIO area that starts at 32TiB. This means that the NVIDIA RAM window starts at 64TiB and go all the way to 128TiB. This means that the guest might request a 64-bit window, for each PCI Host Bridge, that goes all the way to 128TiB. However, the NVIDIA RAM window isn't counted as regular RAM, thus this window is considered only for the allocation of the Translation and Control Entry (TCE). For more information about how NVLink2 support works in QEMU, refer to the accepted implementation [1]. This memory layout differs from the existing VFIO case, requiring its own formula. This patch changes the PPC64 code of @qemuDomainGetMemLockLimitBytes to: - detect if we have a NVLink2 bridge being passed through to the guest. This is done by using the @ppc64VFIODeviceIsNV2Bridge function added in the previous patch. The existence of the NVLink2 bridge in the guest means that we are dealing with the NVLink2 memory layout; - if an IBM NVLink2 bridge exists, passthroughLimit is calculated in a different way to account for the extra memory the TCE table can alloc. The 64TiB..128TiB window is more than enough to fit all possible GPUs, thus the memLimit is the same regardless of passing through 1 or multiple V100 GPUs. Further reading explaining the background [1] https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg03700.html [2] https://www.redhat.com/archives/libvir-list/2019-March/msg00660.html [3] https://www.redhat.com/archives/libvir-list/2019-April/msg00527.html Signed-off-by: Daniel Henrique Barboza <danielhb413(a)gmail.com> Reviewed-by: Erik Skultety <eskultet(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/4a0f604dd031...1a922648f67f View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/520132086?utm_medium=notificat… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

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

13 Apr '19

See <https://ci.centos.org/job/libvirt-rpm/systems=libvirt-fedora-rawhide/355/di…> ------------------------------------------ [...truncated 6.69 MB...] 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> 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-fedora-rawhide/ws/bui…'> FAILED 411) cpuTestCPUIDSignature(x86_64): Xeon-X5460 ... OK FAIL cputest (exit status: 1) + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.zqLkj8 (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.zqLkj8 (%check) Build step 'Execute shell' marked build as failure

1 2

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

13 Apr '19

See <https://ci.centos.org/job/libvirt-rpm/systems=libvirt-fedora-29/355/display…> ------------------------------------------ [...truncated 6.68 MB...] 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> 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-fedora-29/ws/build/rp…'> FAILED 411) cpuTestCPUIDSignature(x86_64): Xeon-X5460 ... OK FAIL cputest (exit status: 1) + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.1KGfSA (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.1KGfSA (%check) Build step 'Execute shell' marked build as failure

1 2

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

13 Apr '19

See <https://ci.centos.org/job/libvirt-rpm/systems=libvirt-fedora-28/355/display…> ------------------------------------------ [...truncated 6.67 MB...] 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> 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-fedora-28/ws/build/rp…'> FAILED 411) cpuTestCPUIDSignature(x86_64): Xeon-X5460 ... OK FAIL cputest (exit status: 1) + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.smGsW1 (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.smGsW1 (%check) Build step 'Execute shell' marked build as failure

1 2

[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

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

13 Apr '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-28/383/…> ------------------------------------------ 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-28 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-28/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins7893994120516352858.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, 42 wallclock secs ( 0.51 usr 0.06 sys + 8.84 cusr 0.65 csys = 10.06 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-fedora-29 #383
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/383/…> ------------------------------------------ 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-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins216237992003344651.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, 37 wallclock secs ( 0.44 usr 0.07 sys + 8.72 cusr 0.69 csys = 9.92 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-freebsd-11 #383
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-11/383…> ------------------------------------------ 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-freebsd-11 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-11/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins3082535883974409239.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 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, 18 wallclock secs ( 0.45 usr 0.28 sys + 13.35 cusr 1.91 csys = 15.98 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-centos-7 #383
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/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-centos-7 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins633614554182094200.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 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, 27 wallclock secs ( 0.47 usr 0.05 sys + 8.34 cusr 0.41 csys = 9.27 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-freebsd-12 #383
by ci＠centos.org 13 Apr '19

13 Apr '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/383…> ------------------------------------------ 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-freebsd-12 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins3072874881024456584.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 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, 20 wallclock secs ( 0.59 usr 0.23 sys + 14.73 cusr 1.55 csys = 17.10 CPU) Result: FAIL Failed 1/12 test programs. 0/1913 subtests failed. Build step 'Execute shell' marked build as failure

1 2

[Libvirt-ci] Still Failing: libvirt/libvirt#2233 (master - 4a0f604)
by Travis CI 13 Apr '19

13 Apr '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2233 Status: Still Failing Duration: 21 mins and 39 secs Commit: 4a0f604 (master) Author: Michal Privoznik Message: cpu_map: Distribute x86_Cascadelake-Server.xml In 2878278c74cc4 we've added new cpu model but we've forgot to distribute the XML file it comes in. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/673f805d4df2...4a0f604dd031 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/519740411?utm_medium=notificat… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

[Libvirt-ci] Still Failing: libvirt/libvirt#2232 (master - 673f805)
by Travis CI 13 Apr '19

13 Apr '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2232 Status: Still Failing Duration: 24 mins and 31 secs Commit: 673f805 (master) Author: Martin Kletzander Message: qemu: Label uniqDir when probing capabilities This does not cause a problem in usual scenarios thanks to us allowing CAP_DAC_OVERRIDE for the qemu process, however in some scenarios this might be an issue because the directory is created with mkdtemp(3) which explicitly creates that with 0700 permissions and qemu running as non-root cannot access that. The scenarios include: - Builds without CAPNG - Running libvirtd in certain container configurations [1] - and possibly others. [1] https://github.com/kubevirt/kubevirt/pull/2181#issuecomment-481840304 Signed-off-by: Martin Kletzander <mkletzan(a)redhat.com> Reviewed-by: Daniel P. Berrangé <berrange(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/df4b46737f43...673f805d4df2 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/519495492?utm_medium=notificat… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

[Libvirt-ci] Broken: libvirt/libvirt#2231 (master - df4b467)
by Travis CI 13 Apr '19

13 Apr '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2231 Status: Broken Duration: 25 mins and 37 secs Commit: df4b467 (master) Author: Jiri Denemark Message: vircpuhost: Add support for reading MSRs The new virHostCPUGetMSR internal API will try to read the MSR from /dev/cpu/0/msr and if it is not possible (the device does not exist or libvirt is running unprivileged), it will fallback to asking KVM for the MSR using KVM_GET_MSRS ioctl. Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com> Reviewed-by: Ján Tomko <jtomko(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/03a07357e1a6...df4b46737f43 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/519470514?utm_medium=notificat… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-rawhide #374
by ci＠centos.org 11 Apr '19

11 Apr '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-rawhi…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 374 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 376 originally caused by: Started by upstream project "libvirt-build" build number 460 originally caused by: 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-go-xml-check/systems=libvirt-fedora-rawhi…> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins7216201601179391221.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (16.21s) xml_test.go:394: testdata/libvirt/tests/domaincapsschemadata/qemu_1.7.0.x86_64.xml: /domainCapabilities[0]/os[0]/enum[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-rawhi…> 16.577s Build step 'Execute shell' marked build as failure

1 6

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-29 #374
by ci＠centos.org 11 Apr '19

11 Apr '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-29/37…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 374 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 376 originally caused by: Started by upstream project "libvirt-build" build number 460 originally caused by: 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-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-29/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins3092104581408274064.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (13.25s) xml_test.go:394: testdata/libvirt/tests/domaincapsschemadata/qemu_1.7.0.x86_64.xml: /domainCapabilities[0]/os[0]/enum[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-29/ws/> 13.481s Build step 'Execute shell' marked build as failure

1 6

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-28 #374
by ci＠centos.org 11 Apr '19

11 Apr '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-28/37…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 374 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 376 originally caused by: Started by upstream project "libvirt-build" build number 460 originally caused by: 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-28 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-28/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins1239770602620454796.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (16.35s) xml_test.go:394: testdata/libvirt/tests/domaincapsschemadata/qemu_1.7.0.x86_64.xml: /domainCapabilities[0]/os[0]/enum[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-28/ws/> 16.538s Build step 'Execute shell' marked build as failure

1 6

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-freebsd-12 #374
by ci＠centos.org 11 Apr '19

11 Apr '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-12/3…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 374 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 376 originally caused by: Started by upstream project "libvirt-build" build number 460 originally caused by: 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-freebsd-12 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-12/w…> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins860213478835965090.sh + export 'TEST_ARGS=-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (5.54s) xml_test.go:394: testdata/libvirt/tests/domaincapsschemadata/qemu_1.7.0.x86_64.xml: /domainCapabilities[0]/os[0]/enum[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _/usr<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-12/w…> 5.613s Build step 'Execute shell' marked build as failure

1 6

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-freebsd-11 #374
by ci＠centos.org 11 Apr '19

11 Apr '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-11/3…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 374 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 376 originally caused by: Started by upstream project "libvirt-build" build number 460 originally caused by: 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-freebsd-11 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-11/w…> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins3387094055070638995.sh + export 'TEST_ARGS=-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (4.46s) xml_test.go:394: testdata/libvirt/tests/domaincapsschemadata/qemu_1.7.0.x86_64.xml: /domainCapabilities[0]/os[0]/enum[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _/usr<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-11/w…> 4.497s Build step 'Execute shell' marked build as failure

1 6

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-debian-9 #374
by ci＠centos.org 11 Apr '19

11 Apr '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-9/374…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 374 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 376 originally caused by: Started by upstream project "libvirt-build" build number 460 originally caused by: 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-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-9/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins7722948974469895373.sh + export TEST_ARGS=-tags xmlroundtrip + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (16.56s) xml_test.go:394: testdata/libvirt/tests/domaincapsschemadata/qemu_1.7.0.x86_64.xml: /domainCapabilities[0]/os[0]/enum[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-9/ws/> 16.680s Build step 'Execute shell' marked build as failure

1 6

[Libvirt-ci] Build failed in Jenkins: libvirt+mingw64-build » libvirt-fedora-rawhide #491
by ci＠centos.org 10 Apr '19

10 Apr '19

See <https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…> Changes: [mprivozn] qemu_firmware: Separate firmware loading into a function [mprivozn] qemu_firmware: Separate machine and arch matching into a function [mprivozn] qemu_firmware: Introduce qemuFirmwareGetSupported [mprivozn] domain capabilities: Expose firmware auto selection feature ------------------------------------------ [...truncated 161.92 KB...] CCLD sockettest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virhostcputest.exe CCLD virbuftest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD commandtest.exe CCLD seclabeltest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virhashtest.exe CCLD virconftest.exe CCLD viratomictest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Could not determine the host path corresponding to libtool: error: Continuing, but uninstalled executables may not work. libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD utiltest.exe CCLD libshunload.la CCLD virtimetest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD viruritest.exe CCLD virkeyfiletest.exe CCLD viralloctest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Could not determine the host path corresponding to libtool: error: Continuing, but uninstalled executables may not work. libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virauthconfigtest.exe CCLD virbitmaptest.exe CCLD vircgrouptest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD vircryptotest.exe CCLD virpcitest.exe CCLD virendiantest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virfiletest.exe CCLD virfilecachetest.exe CCLD virfirewalltest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Could not determine the host path corresponding to libtool: error: Continuing, but uninstalled executables may not work. libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '/usr/x86_64-w64-mingw32/sys-root/mingw/lib:/usr/x86_64-w64-mingw32/sys-root/mingw/bin:<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD viriscsitest.exe CCLD virkeycodetest.exe CCLD virlockspacetest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virlogtest.exe CCLD virrotatingfiletest.exe CCLD virschematest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '/usr/x86_64-w64-mingw32/sys-root/mingw/lib:/usr/x86_64-w64-mingw32/sys-root/mingw/bin:<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virstringtest.exe CCLD virportallocatortest.exe CCLD sysinfotest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virkmodtest.exe CCLD vircapstest.exe CCLD domaincapstest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to domaincapstest.o: In function `mymain': <https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:479: undefined reference to `virFileWrapperClearPrefixes' collect2: error: ld returned 1 exit status gmake[2]: *** [Makefile:5016: domaincapstest.exe] Error 1 gmake[2]: *** Waiting for unfinished jobs.... libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/x86_64-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> gmake[1]: *** [Makefile:2125: all-recursive] Error 1 gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw64-build/systems=libvirt-fedora-rawh…'> gmake: *** [Makefile:2018: all] Error 2 Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: libvirt+mingw32-build » libvirt-fedora-rawhide #491
by ci＠centos.org 10 Apr '19

10 Apr '19

See <https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…> Changes: [mprivozn] qemu_firmware: Separate firmware loading into a function [mprivozn] qemu_firmware: Separate machine and arch matching into a function [mprivozn] qemu_firmware: Introduce qemuFirmwareGetSupported [mprivozn] domain capabilities: Expose firmware auto selection feature ------------------------------------------ [...truncated 160.81 KB...] CCLD virhostcputest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virbuftest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD commandtest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD seclabeltest.exe CCLD virhashtest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virconftest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD viratomictest.exe CCLD utiltest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD libshunload.la libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virtimetest.exe CCLD viruritest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Could not determine the host path corresponding to libtool: error: Continuing, but uninstalled executables may not work. libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. CCLD virkeyfiletest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD viralloctest.exe CCLD virauthconfigtest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virbitmaptest.exe CCLD vircgrouptest.exe CCLD vircryptotest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virpcitest.exe CCLD virendiantest.exe CCLD virfiletest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virfilecachetest.exe CCLD virfirewalltest.exe CCLD viriscsitest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: '/usr/i686-w64-mingw32/sys-root/mingw/lib:/usr/i686-w64-mingw32/sys-root/mingw/bin:<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' CCLD virkeycodetest.exe libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Continuing, but uninstalled executables may not work. CCLD virlockspacetest.exe CCLD virlogtest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> CCLD virrotatingfiletest.exe libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD virschematest.exe CCLD virstringtest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> CCLD virportallocatortest.exe libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '/usr/i686-w64-mingw32/sys-root/mingw/lib:/usr/i686-w64-mingw32/sys-root/mingw/bin:<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD sysinfotest.exe CCLD virkmodtest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Could not determine the host path corresponding to libtool: error: Continuing, but uninstalled executables may not work. libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. CCLD vircapstest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. CCLD domaincapstest.exe CCLD domainconftest.exe libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. domaincapstest.o: In function `mymain': <https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:479: undefined reference to `virFileWrapperClearPrefixes' collect2: error: ld returned 1 exit status gmake[2]: *** [Makefile:5016: domaincapstest.exe] Error 1 gmake[2]: *** Waiting for unfinished jobs.... libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> libtool: error: Continuing, but uninstalled executables may not work. libtool: error: Could not determine the host path corresponding to libtool: error: '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…>:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/lib:/home/jenkins/build/libvirt/i686-w64-mingw32/sys-root/mingw/bin' libtool: error: Continuing, but uninstalled executables may not work. gmake[2]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> gmake[1]: *** [Makefile:2125: all-recursive] Error 1 gmake[1]: Leaving directory '<https://ci.centos.org/job/libvirt+mingw32-build/systems=libvirt-fedora-rawh…'> gmake: *** [Makefile:2018: all] Error 2 Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Fixed: libvirt/libvirt#2214 (master - 947ea86)
by Travis CI 10 Apr '19

10 Apr '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2214 Status: Fixed Duration: 23 mins and 21 secs Commit: 947ea86 (master) Author: Andrea Bolognani Message: tests: Fix MinGW build for domaincapstest Commit 5b9819eedc71 started using the virFileWrapper APIs in the test program, and correctly called them only in the section of code guarded by WITH_QEMU; however, a single call to the virFileWrapperClearPrefixes() function ended up in the hypervisor-agnostic section, causing a build failure on MinGW. Move the call to the QEMU-only section; while at it, also drop the virFileWrapperRemovePrefix() calls, which are entirely redundant since we'd drop all prefixes immediately afterwards anyway. Signed-off-by: Andrea Bolognani <abologna(a)redhat.com> Acked-by: Michal Privoznik <mprivozn(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/5b9819eedc71...947ea8665e4e View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/518319081?utm_medium=notificat… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

[Libvirt-ci] Broken: libvirt/libvirt#2213 (master - 5b9819e)
by Travis CI 10 Apr '19

10 Apr '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2213 Status: Broken Duration: 21 mins and 33 secs Commit: 5b9819e (master) Author: Michal Privoznik Message: domain capabilities: Expose firmware auto selection feature If a management application wants to use firmware auto selection feature it can't currently know if the libvirtd it's talking to support is or not. Moreover, it doesn't know which values that are accepted for the @firmware attribute of <os/> when parsing will allow successful start of the domain later, i.e. if the mgmt application wants to use 'bios' whether there exists a FW descriptor in the system that describes bios. This commit then adds 'firmware' enum to <os/> element in <domainCapabilities/> XML like this: <enum name='firmware'> <value>bios</value> <value>efi</value> </enum> We can see both 'bios' and 'efi' listed which means that there are descriptors for both found in the system (matched with the machine type and architecture reported in the domain capabilities earlier and not shown here). Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Acked-by: Laszlo Ersek <lersek(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/f7853181878d...5b9819eedc71 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/518271098?utm_medium=notificat… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

1 0

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

10 Apr '19

See <https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/13…> ------------------------------------------ Started by upstream project "libosinfo-check" build number 139 originally caused by: Started by upstream project "libosinfo-syntax-check" build number 142 originally caused by: Started by upstream project "libosinfo-build" build number 145 originally caused by: Started by upstream project "osinfo-db-build" build number 88 originally caused by: 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/libosinfo-check/systems=libvirt-fedora-rawhide/ws/> [libosinfo] $ /bin/sh -xe /tmp/jenkins7692372989050115046.sh + cd build + /usr/bin/gmake check GEN public-submodule-commit Making check in osinfo gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> /usr/bin/gmake check-am gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> /usr/bin/gmake check-local gmake[3]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> GEN check-symfile GEN check-symsorting gmake[3]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> Making check in tools gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> Making check in docs gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> Making check in reference gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[2]: Nothing to be done for 'check'. gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[2]: Nothing to be done for 'check-am'. gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> Making check in po gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> Making check in examples gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> Making check in tests gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> /usr/bin/gmake test-entity test-device test-list test-devicelist test-devicelinklist test-filter test-media test-product test-os test-oslist test-productfilter test-platform test-platformlist test-db test-loader test-install-script test-image test-imagelist test-tree gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> CC test_entity-test-entity.o CC test_device-test-device.o CC test_list-test-list.o CC test_devicelist-test-devicelist.o CC test_devicelinklist-test-devicelinklist.o CC test_filter-test-filter.o CC test_media-test-media.o CC test_product-test-product.o CC test_os-test-os.o CC test_oslist-test-oslist.o CC test_productfilter-test-productfilter.o CC test_platform-test-platform.o CC test_platformlist-test-platformlist.o CC test_db-test-db.o CC test_loader-test-loader.o CC test_install_script-test-install-script.o CC test_image-test-image.o CC test_imagelist-test-imagelist.o CC test_tree-test-tree.o CCLD test-entity CCLD test-device CCLD test-list CCLD test-devicelist CCLD test-devicelinklist CCLD test-filter CCLD test-media CCLD test-product CCLD test-os CCLD test-oslist CCLD test-productfilter CCLD test-platform CCLD test-platformlist CCLD test-db CCLD test-loader CCLD test-install-script CCLD test-image CCLD test-imagelist CCLD test-tree gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> /usr/bin/gmake check-TESTS gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[3]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> PASS: test-entity PASS: test-device PASS: test-list PASS: test-devicelist PASS: test-devicelinklist PASS: test-filter PASS: test-product PASS: test-media PASS: test-os PASS: test-oslist PASS: test-productfilter PASS: test-platform PASS: test-platformlist PASS: test-db PASS: test-image PASS: test-install-script PASS: test-imagelist PASS: test-tree ../../build-aux/test-driver: line 107: 31439 Trace/breakpoint trap (core dumped) "$@" > $log_file 2>&1 FAIL: test-loader ============================================================================ Testsuite summary for libosinfo 1.5.0 ============================================================================ # TOTAL: 19 # PASS: 18 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/test-suite.log Please report to libosinfo(a)redhat.com ============================================================================ gmake[3]: *** [Makefile:1333: test-suite.log] Error 1 gmake[3]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[2]: *** [Makefile:1441: check-TESTS] Error 2 gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake[1]: *** [Makefile:1641: check-am] Error 2 gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-rawhide/ws…'> gmake: *** [Makefile:585: check-recursive] Error 1 + cat tests/test-suite.log =========================================== libosinfo 1.5.0: tests/test-suite.log =========================================== # TOTAL: 19 # PASS: 18 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-loader ================= /loader/basic: ** (./test-loader:31439): CRITICAL **: 09:55:10.662: osinfo_entity_set_param: assertion 'value != NULL' failed FAIL test-loader (exit status: 133) + exit 1 Build step 'Execute shell' marked build as failure

1 2

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

10 Apr '19

See <https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/139/dis…> ------------------------------------------ Started by upstream project "libosinfo-check" build number 139 originally caused by: Started by upstream project "libosinfo-syntax-check" build number 142 originally caused by: Started by upstream project "libosinfo-build" build number 145 originally caused by: Started by upstream project "osinfo-db-build" build number 88 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/> [libosinfo] $ /bin/sh -xe /tmp/jenkins2257580938336440099.sh + cd build + /usr/bin/gmake check GEN public-submodule-commit Making check in osinfo gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> /usr/bin/gmake check-am gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> /usr/bin/gmake check-local gmake[3]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> GEN check-symfile GEN check-symsorting gmake[3]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> Making check in tools gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> Making check in docs gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> Making check in reference gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[2]: Nothing to be done for 'check'. gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[2]: Nothing to be done for 'check-am'. gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> Making check in po gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> Making check in examples gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> Making check in tests gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> /usr/bin/gmake test-entity test-device test-list test-devicelist test-devicelinklist test-filter test-media test-product test-os test-oslist test-productfilter test-platform test-platformlist test-db test-loader test-install-script test-image test-imagelist test-tree gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> CC test_entity-test-entity.o CC test_device-test-device.o CC test_list-test-list.o CC test_devicelist-test-devicelist.o CC test_devicelinklist-test-devicelinklist.o CC test_filter-test-filter.o CC test_media-test-media.o CC test_product-test-product.o CC test_oslist-test-oslist.o CC test_os-test-os.o CC test_productfilter-test-productfilter.o CC test_platform-test-platform.o CC test_platformlist-test-platformlist.o CC test_db-test-db.o CC test_loader-test-loader.o CC test_install_script-test-install-script.o CC test_image-test-image.o CC test_imagelist-test-imagelist.o CC test_tree-test-tree.o CCLD test-entity CCLD test-device CCLD test-list CCLD test-devicelist CCLD test-devicelinklist CCLD test-filter CCLD test-media CCLD test-product CCLD test-os CCLD test-oslist CCLD test-productfilter CCLD test-platform CCLD test-platformlist CCLD test-db CCLD test-loader CCLD test-install-script CCLD test-image CCLD test-imagelist CCLD test-tree gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> /usr/bin/gmake check-TESTS gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[3]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> PASS: test-list PASS: test-device PASS: test-entity PASS: test-devicelist PASS: test-filter PASS: test-devicelinklist PASS: test-product PASS: test-media PASS: test-oslist PASS: test-productfilter PASS: test-os PASS: test-platformlist PASS: test-platform PASS: test-db PASS: test-image PASS: test-install-script PASS: test-imagelist PASS: test-tree ../../build-aux/test-driver: line 107: 25639 Trace/breakpoint trap (core dumped) "$@" > $log_file 2>&1 FAIL: test-loader ============================================================================ Testsuite summary for libosinfo 1.5.0 ============================================================================ # TOTAL: 19 # PASS: 18 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/test-suite.log Please report to libosinfo(a)redhat.com ============================================================================ gmake[3]: *** [Makefile:1333: test-suite.log] Error 1 gmake[3]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[2]: *** [Makefile:1441: check-TESTS] Error 2 gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake[1]: *** [Makefile:1641: check-am] Error 2 gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-29/ws/buil…'> gmake: *** [Makefile:585: check-recursive] Error 1 + cat tests/test-suite.log =========================================== libosinfo 1.5.0: tests/test-suite.log =========================================== # TOTAL: 19 # PASS: 18 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-loader ================= /loader/basic: ** (./test-loader:25639): CRITICAL **: 09:54:43.371: osinfo_entity_set_param: assertion 'value != NULL' failed FAIL test-loader (exit status: 133) + exit 1 Build step 'Execute shell' marked build as failure

1 2

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

10 Apr '19

See <https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/139/dis…> ------------------------------------------ Started by upstream project "libosinfo-check" build number 139 originally caused by: Started by upstream project "libosinfo-syntax-check" build number 142 originally caused by: Started by upstream project "libosinfo-build" build number 145 originally caused by: Started by upstream project "osinfo-db-build" build number 88 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-28 (libvirt) in workspace <https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/> [libosinfo] $ /bin/sh -xe /tmp/jenkins5717742975306495664.sh + cd build + /usr/bin/gmake check GEN public-submodule-commit Making check in osinfo gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> /usr/bin/gmake check-am gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> /usr/bin/gmake check-local gmake[3]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> GEN check-symfile GEN check-symsorting gmake[3]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> Making check in tools gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> Making check in docs gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> Making check in reference gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[2]: Nothing to be done for 'check'. gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[2]: Nothing to be done for 'check-am'. gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> Making check in po gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> Making check in examples gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[1]: Nothing to be done for 'check'. gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> Making check in tests gmake[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> /usr/bin/gmake test-entity test-device test-list test-devicelist test-devicelinklist test-filter test-media test-product test-os test-oslist test-productfilter test-platform test-platformlist test-db test-loader test-install-script test-image test-imagelist test-tree gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> CC test_entity-test-entity.o CC test_list-test-list.o CC test_device-test-device.o CC test_devicelist-test-devicelist.o CC test_devicelinklist-test-devicelinklist.o CC test_filter-test-filter.o CC test_media-test-media.o CC test_product-test-product.o CC test_os-test-os.o CC test_oslist-test-oslist.o CC test_productfilter-test-productfilter.o CC test_platform-test-platform.o CC test_platformlist-test-platformlist.o CC test_db-test-db.o CC test_loader-test-loader.o CC test_install_script-test-install-script.o CC test_image-test-image.o CC test_imagelist-test-imagelist.o CC test_tree-test-tree.o CCLD test-entity CCLD test-device CCLD test-list CCLD test-devicelist CCLD test-devicelinklist CCLD test-filter CCLD test-media CCLD test-product CCLD test-os CCLD test-oslist CCLD test-productfilter CCLD test-platform CCLD test-platformlist CCLD test-db CCLD test-loader CCLD test-install-script CCLD test-image CCLD test-imagelist CCLD test-tree gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> /usr/bin/gmake check-TESTS gmake[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[3]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> PASS: test-device PASS: test-entity PASS: test-list PASS: test-devicelinklist PASS: test-filter PASS: test-devicelist PASS: test-product PASS: test-media PASS: test-oslist PASS: test-productfilter PASS: test-os PASS: test-platformlist PASS: test-platform PASS: test-db PASS: test-install-script PASS: test-image PASS: test-tree PASS: test-imagelist ../../build-aux/test-driver: line 107: 30644 Trace/breakpoint trap (core dumped) "$@" > $log_file 2>&1 FAIL: test-loader ============================================================================ Testsuite summary for libosinfo 1.5.0 ============================================================================ # TOTAL: 19 # PASS: 18 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/test-suite.log Please report to libosinfo(a)redhat.com ============================================================================ gmake[3]: *** [Makefile:1308: test-suite.log] Error 1 gmake[3]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[2]: *** [Makefile:1416: check-TESTS] Error 2 gmake[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake[1]: *** [Makefile:1613: check-am] Error 2 gmake[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-fedora-28/ws/buil…'> gmake: *** [Makefile:585: check-recursive] Error 1 + cat tests/test-suite.log =========================================== libosinfo 1.5.0: tests/test-suite.log =========================================== # TOTAL: 19 # PASS: 18 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-loader ================= /loader/basic: ** (./test-loader:30644): CRITICAL **: 09:54:43.639: osinfo_entity_set_param: assertion 'value != NULL' failed FAIL test-loader (exit status: 133) + exit 1 Build step 'Execute shell' marked build as failure

1 2

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

10 Apr '19

See <https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/139/disp…> ------------------------------------------ Started by upstream project "libosinfo-check" build number 139 originally caused by: Started by upstream project "libosinfo-syntax-check" build number 142 originally caused by: Started by upstream project "libosinfo-build" build number 145 originally caused by: Started by upstream project "osinfo-db-build" build number 88 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/> [libosinfo] $ /bin/sh -xe /tmp/jenkins226112842990398667.sh + cd build + /usr/bin/make check GEN public-submodule-commit Making check in osinfo make[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> /usr/bin/make check-am make[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> /usr/bin/make check-local make[3]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> GEN check-symfile GEN check-symsorting make[3]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> make[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> make[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> Making check in tools make[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> Making check in docs make[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> Making check in reference make[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> make[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> make[2]: Nothing to be done for 'check-am'. make[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> make[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> Making check in po make[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> Making check in examples make[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> Making check in tests make[1]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> /usr/bin/make test-entity test-device test-list test-devicelist test-devicelinklist test-filter test-media test-product test-os test-oslist test-productfilter test-platform test-platformlist test-db test-loader test-install-script test-image test-imagelist test-tree make[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> CC test_entity-test-entity.o CC test_list-test-list.o CC test_device-test-device.o CC test_devicelist-test-devicelist.o CC test_devicelinklist-test-devicelinklist.o CC test_media-test-media.o CC test_filter-test-filter.o CC test_product-test-product.o CC test_os-test-os.o CC test_oslist-test-oslist.o CC test_productfilter-test-productfilter.o CC test_platform-test-platform.o CC test_platformlist-test-platformlist.o CC test_db-test-db.o CC test_loader-test-loader.o CC test_install_script-test-install-script.o CC test_image-test-image.o CC test_imagelist-test-imagelist.o CC test_tree-test-tree.o CCLD test-entity CCLD test-device CCLD test-list CCLD test-devicelist CCLD test-devicelinklist CCLD test-filter CCLD test-media CCLD test-product CCLD test-os CCLD test-oslist CCLD test-productfilter CCLD test-platform CCLD test-platformlist CCLD test-db CCLD test-loader CCLD test-install-script CCLD test-image CCLD test-imagelist CCLD test-tree make[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> /usr/bin/make check-TESTS make[2]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> make[3]: Entering directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> PASS: test-device PASS: test-list PASS: test-entity PASS: test-devicelist PASS: test-devicelinklist PASS: test-filter PASS: test-product PASS: test-oslist PASS: test-media PASS: test-productfilter PASS: test-platformlist PASS: test-os PASS: test-platform PASS: test-db PASS: test-image PASS: test-install-script PASS: test-imagelist PASS: test-tree ../../build-aux/test-driver: line 107: 9581 Trace/breakpoint trap "$@" > $log_file 2>&1 FAIL: test-loader ============================================================================ Testsuite summary for libosinfo 1.5.0 ============================================================================ # TOTAL: 19 # PASS: 18 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/test-suite.log Please report to libosinfo(a)redhat.com ============================================================================ Makefile:1308: recipe for target 'test-suite.log' failed make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> Makefile:1414: recipe for target 'check-TESTS' failed make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> Makefile:1613: recipe for target 'check-am' failed make[1]: *** [check-am] Error 2 make[1]: Leaving directory '<https://ci.centos.org/job/libosinfo-check/systems=libvirt-debian-9/ws/build…'> Makefile:586: recipe for target 'check-recursive' failed make: *** [check-recursive] Error 1 + cat tests/test-suite.log =========================================== libosinfo 1.5.0: tests/test-suite.log =========================================== # TOTAL: 19 # PASS: 18 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-loader ================= /loader/basic: ** (./test-loader:9581): CRITICAL **: osinfo_entity_set_param: assertion 'value != NULL' failed FAIL test-loader (exit status: 133) + exit 1 Build step 'Execute shell' marked build as failure

1 2