On 17 March 2014 14:31, Greg Clayton <[email protected]> wrote: > The patch below adds a new "--threads" option whose default value is > "multiprocessing.cpu_count()". And only if "multiprocessing.cpu_count()" > returns 0 will it fall back to using the LLDB_TEST_THREADS environment > variable. I am not sure why the environment variable was ever used instead of > using an option. > > If everyone can try out this patch and make sure it does things as expected:
It gets the correct number of threads by default for me. Looks like you'll want to clean up the messages about the env variable though: default: Running tests with 8 threads Running multithreaded with 8 threads (from LLDB_TEST_THREADS) or w/ --threads 1: Running tests with 1 threads NOT running multithreaded. Consider setting LLDB_TEST_THREADS environment variable. _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
