I actually am seeing this now, I'm not sure why I didn't see it earlier,
the only thing I can think of is that the patch didn't apply successfully
even though I thoguht it did.
When I stop at this line:
if num_threads > 1:
pool = multiprocessing.Pool(
num_threads,
initializer=setup_global_variables,
initargs=(output_lock, test_counter, total_tests, test_name_len,
dotest_options))
in a debugger and inspect the value of dotest_options,
`dotest_options.no_multiprocessing` is set to False. Is this correct? It
seems like for the child dotest instances, it shouldn't be trying to
recursively do this multiprocessing?
On Thu, Sep 3, 2015 at 3:13 PM Zachary Turner <ztur...@google.com> wrote:
> zturner added a comment.
>
> I didn't see this when I ran ninja check-lldb, but Adrian is seeing the
> same thing on his machine for some reason.
>
>
> http://reviews.llvm.org/D12587
>
>
>
>
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
