fork mode ............................ yes high resolution timer replacement .... no snprintf replacement ................. no subunit support....................... no timeout unit tests ................... yes POSIX regular expressions ............ yes ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-libressl_test-20200126-104546 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * clang: clang version 9.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/9/bin llvm: 9.0.1 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) [5] pypy3 (fallback) Available Rust versions: [1] rust-1.40.0 * java-config: The following VMs are available for generation-2: *) AdoptOpenJDK JRE 8.242_p08 [openjdk-jre-bin-8] Available Java Virtual Machines: [1] openjdk-jre-bin-8 system-vm ghc: The Glorious Glasgow Haskell Compilation System, version 8.0.2 repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Sun, 02 Feb 2020 09:27:58 +0000 emerge -qpvO dev-libs/check [ebuild U ] dev-libs/check-0.14.0 [0.13.0] USE="test* -doc -static-libs -subunit" ABI_X86="(64) -32 (-x32)"
Created attachment 610996 [details] emerge-info.txt
Created attachment 610998 [details] dev-libs:check-0.14.0:20200202-102016.log
Created attachment 611000 [details] emerge-history.txt
Created attachment 611002 [details] environment
Created attachment 611004 [details] etc.portage.tbz2
Created attachment 611006 [details] logs.tbz2
Created attachment 611008 [details] temp.tbz2
Created attachment 611010 [details] tests.tbz2
The test suite no longer fails for me with dev-libs/check-0.14.0-r1, but the output (tests run) also look different. The tests that failed for 0.14.0 are apparently no longer run. >>> Test phase: dev-libs/check-0.14.0-r1 * abi_x86_64.amd64: running multilib-minimal_abi_src_test * Working in BUILD_DIR: "/var/tmp/portage/dev-libs/check-0.14.0-r1/work/check-0.14.0_build-abi_x86_64.amd64" ctest -j 8 --test-load 999 Test project /var/tmp/portage/dev-libs/check-0.14.0-r1/work/check-0.14.0_build-abi_x86_64.amd64 Start 1: check_check Start 2: check_check_export Start 3: test_output.sh Start 4: test_log_output.sh Start 5: test_xml_output.sh Start 6: test_tap_output.sh Start 7: test_check_nofork.sh Start 8: test_check_nofork_teardown.sh 1/9 Test #7: test_check_nofork.sh ............. Passed 0.01 sec Start 9: test_set_max_msg_size.sh 2/9 Test #8: test_check_nofork_teardown.sh .... Passed 0.01 sec 3/9 Test #9: test_set_max_msg_size.sh ......... Passed 0.04 sec 4/9 Test #6: test_tap_output.sh ............... Passed 0.06 sec 5/9 Test #4: test_log_output.sh ............... Passed 0.09 sec 6/9 Test #5: test_xml_output.sh ............... Passed 0.13 sec 7/9 Test #3: test_output.sh ................... Passed 0.16 sec 8/9 Test #2: check_check_export ............... Passed 175.38 sec 9/9 Test #1: check_check ...................... Passed 175.47 sec 100% tests passed, 0 tests failed out of 9 Total Test time (real) = 175.47 sec * Tests succeeded. >>> Completed testing dev-libs/check-0.14.0-r1
The problematic and failed tests should be these ones: (In reply to tka from comment #9) > Start 1: check_check > Start 2: check_check_export > 8/9 Test #2: check_check_export ............... Passed 175.38 sec > 9/9 Test #1: check_check ...................... Passed 175.47 sec Which now pass happily. The output can look different because with CMake even ABI_32 tests are run properly, and a previous patch about assertion failures isn't being applied anymore. Btw I forgot about this, there is a 2nd bug open about same issue (I think?) https://bugs.gentoo.org/711390 more discussion here.
Should be fixed with a version bump, https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6696321039a54c96e21cbb3b01d0fdcec4d70e70
