https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89255
--- Comment #6 from Iain Buclaw <ibuclaw at gdcproject dot org> --- Created attachment 46069 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46069&action=edit Use dg-runtest instead of dg-test (In reply to Iain Buclaw from comment #4) > (In reply to r...@cebitec.uni-bielefeld.de from comment #3) > > > > FAIL: libphobos.shared/finalize.d -shared-libphobos -ldl execution test > > FAIL: libphobos.shared/finalize.d -shared-libphobos -ldl execution test > > FAIL: libphobos.shared/finalize.d -shared-libphobos -ldl execution test > > FAIL: libphobos.shared/finalize.d -shared-libphobos -ldl execution test > > FAIL: libphobos.shared/finalize.d -shared-libphobos -ldl execution test > > FAIL: libphobos.shared/finalize.d -shared-libphobos -ldl execution test > > FAIL: libphobos.shared/finalize.d -shared-libphobos -ldl execution test > > FAIL: libphobos.shared/finalize.d -shared-libphobos -ldl execution test > > FAIL: libphobos.shared/finalize.d -shared-libphobos -ldl execution test > > FAIL: libphobos.shared/finalize.d -shared-libphobos -ldl execution test > > > > compilation is run 10 times in exactly the same way!? > > > > Maybe something is missing in the part copied from GCC_RUNTEST_PARALLELIZE. > I did see problems copying gcc_parallel_test_run_p and other procedures > locally to the libphobos testsuite, it looked like it replaced itself > incorrectly. Ahh, we're calling dg-test directly, instead of dg-runtest, so there's no protection against parallelized tests. Looking at dejagnu/dg.exp, there's no reason to use dg-test, so switching all over.
