44 - gtest_no_rtti_unittest (SEGFAULT) 46 - gtest_use_own_tuple_test (SEGFAULT) 51 - gtest_filter_unittest (Failed) Errors while running CTest * ERROR: dev-cpp/gtest-1.8.0-r1::gentoo failed (test phase): * Tests failed. When you file a bug, please attach the following file: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_abi32+64-test_20180501-232814 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 [2] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) emerge -qpv dev-cpp/gtest [ebuild N ] dev-cpp/gtest-1.8.0-r1 USE="{test} -doc -examples" ABI_X86="32 (64) (-x32)"
Created attachment 529312 [details] emerge-info.txt
Created attachment 529314 [details] dev-cpp:gtest-1.8.0-r1:20180502-031418.log
Created attachment 529316 [details] emerge-history.txt
Created attachment 529318 [details] environment
Created attachment 529320 [details] etc.portage.tbz2
Created attachment 529322 [details] LastTest.log.bz2
Created attachment 529324 [details] logs.tbz2
Created attachment 529326 [details] temp.tbz2
Created attachment 529328 [details] tests.tbz2
Thanks for all the info. Unfortunately, I am unable to reproduce the issue even with the same FEATURES and USE flags. The test log shows failures of some subtests but such failures also exist in the log on my end when all tests pass so AFAIK they are supposed to fail. I believe GTest is supposed to use gtest_break_on_failure_unittest.py wrapper to handle all segfault signals that are expected to occur. If you are able to reproduce this bug, please post any relevant messages from dmesg if they exist. Either way, I'll leave the bug up for now in case others run into it.
Given that the tests failed with python3 and support for building with python3 was removed for similar reasons with https://gitweb.gentoo.org/repo/gentoo.git/commit/dev-cpp/gtest?id=29813dfe9222aa81b9706f29dbb5d91bc0a81c55, I will assume this is fixed. Reopen if reproducible.
