https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-libs/castxml-0.5.1 fails tests (LIBARCHIVE-SYSTEM). Discovered on: amd64 (internal ref: libarchive_tinderbox) NOTE: (LIBARCHIVE-SYSTEM) in the summary means that the bug was found on a machine that runs app-alternatives/tar and app-alternatives/cpio with [-gnu,+libarchive] but this bug MAY or MAY NOT BE related to the tar/cpio implementation.
Created attachment 849071 [details] build.log build log and emerge --info
Created attachment 849073 [details] 1-LastTest.log.xz 1-LastTest.log (compressed because it exceeds attachment limit, use 'xzless' to read it)
Seems not related to the LIBATCHIVE-SYSTEM. Fails also with app-alternatives/tar with [+gnu, -libarchive]. It is weird that it now fails, as I fixed the test suite just 10 days before.
As it turns out the bump from clang-15.06 to clang-15.0.7 is the main culprit for the failing tests. There seems to be two different factors - For some of the tests the expected output (checked by the test suite) changed so that it gets not recognized as valid. There seems to be only a minority of the failing tests with that reason. - For a quite large number of tests castxml just fails to run with something like "unsupported option '-fPIE' for target 'i386-pc-windows-msvc'" or similar. It seems questionable to keep the tests in place if they are so brittle with regard to minor changes of the underlying clang version.
*** Bug 895394 has been marked as a duplicate of this bug. ***
Did some further test with clang-15.0.7 on a different distribution (Linux MINT). All Tests runs without problems there. So it seems to be the 'gentoo way' we use in the clang config files. Further tests showed that the mayor of the failed tests (around 500) are a result of gentoo-hardened.cfg especially the '-fPIE' flag. Further 10 failed tests are a result of including 'maybe-stddefs.h'.
