On Wed, Feb 20, 2019 at 02:31:37PM +0100, Tomasz Kłoczko wrote: > Recently I've been trying to trace some gcc issue so I've downloaded my gcc > src.rpm to try to build my own package. > During review build log I found a lot of test suite failures. > Initially I've been thinking that something is wrong with my devel env so > I've peaked on official gcc build logs and I found that I have even less > such failures than number of such issues on rawhide builders. The aim is to avoid regressions, not zero FAIL rate, which e.g. for the guality testcase is not really possible as the testing matrix is too large for debug info coverage, -O levels x targets x ISA choices x GDB issues and it is impossible to encode that into xfails. Plus, the rpm builds test both normally and with additional -fstack-protector-strong as that is what the whole distro does, while normally the latter isn't included. So, some FAILs might be once with normal options and once with -fstack-protector-strong, other tests only FAIL with the latter e.g. when testing asan and having UB in the test to test it how asan handles it and -fstack-protector-strong may stand in a way of that. There are some flakey tests too (mostly in the go testsuite). So, I have a directory with years of testsuite results from koji/brew builds, essentially build logs from all the architectures massaged through sed -n -e '/^==*TESTING/,/^==*TESTING END/p' and compare that regularly for new builds. Jakub _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
