On May 18, 2005, at 11:20 AM, Martin Wille wrote:
Douglas Gregor wrote:
Today, all of the iostreams tests seem to be looping for me. Any idea what happened?
The same happens here.
I suggest we add something like
ulimit -m 524288; ulimit -d 524288; ulimit -v 523288; ulimit -t 600
to the script that runs the tests on Unix systems to make problems like this not break the testing procedure for everyone. (This sets memory limits to 512 MB and the CPU time limit to 600 seconds. There's no easy way of limiting the wall clock time taken.) Perhaps, the limits should be set even lower.
300 seconds should be sufficient. We can't just do this in regression.py, because we don't want it to apply to the entire bjam run. Instead, we need to set the ulimits when bjam invokes individual test cases. If a bjam expert doesn't pop up with help, I'll take a shot at it later today. Doug