Jakub Jelinek <ja...@redhat.com> writes:
> I guess [getenv GCC_TEST_RUN_EXPENSIVE] != "" could be a usable test here,
> if false it could always use 64 threads or something like that, if true
> it should IMNSHO still bound it to at most max($[`ulimit -u`/2], 10000)
> when ulimit -u is available, because running the thread when it is known
> to break other things is a bad idea.
Right.
> But of course if Ian wants to guard networking libgo tests with some env
> var, GCC_TEST_RUN_EXPENSIVE probably isn't an env var to use...
Indeed, although I'd prefer a different solution, as outlined in PR
go/48017.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
