https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: sys-apps/portage-3.0.38.1-r2 fails tests (LTO-SYSTEM). Discovered on: amd64 (internal ref: lto_tinderbox) NOTE: (LTO-SYSTEM) in the summary means that bug was found on a machine that runs lto but this bug MAY or MAY NOT BE related to lto. This machine uses lto with CFLAGS=-flto -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing Here is a bit of explanation: -Werror=lto-type-mismatch: User to find possible runtime issues in packages. It likely means the package is unsafe to build & use with LTO. For projects using the same identifier but with different types across different files, they must be fixed to be consistent across the codebase. -Werror=odr: Used to find possible runtime issues in packages. These bugs are a problem anyway but may be even worse when combined with LTO. C++ code must comply with the One Definition Rule (ODR) - see https://en.cppreference.com/w/cpp/language/definition#One_Definition_Rule. -Werror=strict-aliasing: Used to find possible runtime issues in packages. These bugs are a problem anyway but may be even worse when combined with LTO. Workarounds: - If upstream is friendly and still active, file a bug upstream. For emulators, codecs, games, or multimedia packages, it may be worth just applying a workaround instead, as upstreams sometimes aren't receptive to these bugs (VALID FOR ALL). - Use the new 'filter-lto' from flag-o-matic.eclass as it's likely to be unsafe with LTO (VALID FOR lto-type-mismatch - odr). - Fix it yourself if interested, of course (VALID FOR ALL). - Append-flags -fno-strict-aliasing (VALID FOR strict-aliasing). - Use memcpy() but a union is sometimes suitable too (VALID FOR strict-aliasing). - -fstrict-aliasing is implied by -O2, so this must be addressed in some form (VALID FOR strict-aliasing). See also: https://marc.info/?l=gentoo-dev&m=165639574126280&w=2
Created attachment 828351 [details] build.log build log and emerge --info
Error(s) that match a know pattern: AssertionError: False is not true FAIL: testOverallTimeoutWithException (portage.tests.util.futures.test_retry.RetryForkExecutorTestCase) FAILED (failures=1) bash: line 1: /var/tmp/portage/sys-apps/portage-3.0.38.1-r2/temp/tmp2p_f343p/var/portage/distfiles/.__portage_test_write__: Permission denied error: could not lock config file /etc/gitconfig: Permission denied subprocess.CalledProcessError: Command '['/usr/bin/pypy3', '-bWd', '/var/tmp/portage/sys-apps/portage-3.0.38.1-r2/work/portage-3.0.38.1-pypy3/lib/portage/tests/runTests.py']' returned non-zero exit status 1. error: could not lock config file /etc/gitconfig: Permission denied
FAIL: testOverallTimeoutWithException (portage.tests.util.futures.test_retry.RetryForkExecutorTestCase)
*** This bug has been marked as a duplicate of bug 850127 ***
