On Fri, Feb 23, 2018 at 11:54:28AM -0600, Jason L Tibbitts III wrote: > >>>>> "JJ" == Jakub Jelinek <jakub@xxxxxxxxxx> writes: > > JJ> Haven't managed to reproduce it, while there are some testsuite > JJ> failures, they are due to timeouts and e.g. dmesg doesn't show any > JJ> segvs nor traps. > > Of course I can reproduce this easily and it also happens in the > buildsystem. The first failure after the gcc update is > https://koji.fedoraproject.org/koji/taskinfo?taskID=25054443 Note that > it fails on all architectures except for s390x, and that succeeds only > because the test suite is disabled there. Well, I'm seeing Suite: backend Test: badhost ...FAILED 1. cunit/unit.c:133 - CU_FAIL_FATAL("Code under test timed out") Test: badservice ... unit: code under test (/builddir/build/BUILD/cyrus-imapd-3.0.5/cunit/backend.testc:test_badhost) timed out passed Test: sasl_plain ...FAILED 1. cunit/unit.c:133 - CU_FAIL_FATAL("Code under test timed out") Test: sasl_digestmd5 ... unit: code under test (/builddir/build/BUILD/cyrus-imapd-3.0.5/cunit/backend.testc:test_sasl_plain) timed out FAILED and many others, supposedly the issue you have is after this make check and thus my mock build doesn't even reach there. Does it need networking outside of the mock (i.e. shall I retry with --enable-networking)? Jakub _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
