https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #3 from Iain Buclaw <ibuclaw at gdcproject dot org> --- (In reply to Jakub Jelinek from comment #0) > The reason I'm filing this is that there are multiple issues: > > 1) what I'm worried about most is that the timeouts for tests don't work, it > happens that some test gets stuck, but it should be killed after 5 minutes > or for how long the default timeout is set and the set should FAIL in that > case or something similar > I couldn't reproduce, maybe I'm running the 32bit testsuite differently though? Running ../../../../../libphobos/testsuite/libphobos.unittests/unittests.exp ... WARNING: program timed out. FAIL: libphobos.unittests/phobos/static/std.net.curl WARNING: program timed out. FAIL: libphobos.unittests/phobos/shared/std.net.curl > 2) if Curl fails to initialize, the test shouldn't get stuck > Patch I've sent upstream fixes this. > 3) and, if libcurl isn't available, I think it would be better to skip the > test as UNSUPPORTED, i.e. add some effective-target that tests if libcurl is > available and if it fails, don't even try to run the test This would be a proc local to libphobos I guess? There's nothing using this module outside of the libphobos testsuite.
