JDevlieghere added a comment. In D65311#1605147 <https://reviews.llvm.org/D65311#1605147>, @jasonmolenda wrote:
> I'm not sure it's really relevant when lit is the driver, but I would often > use --no-multiprocess with dotest to see the full trace output of a single > test while it was running. In multiprocess mode that wasn't displayed iirc. > That's my only use of it. I do use --threads 1 when doing a testsuite run > against a device because there's some buggy behavior in the lldb testsuite > when running multiple tests simultaneously on a remote device (at least a > remote darwin device). But I'm sure you're not talking about removing that > control. Yup, at this point I'm just removing multiprocessing support. However, the ultimate goal is to have no driving capabilities in dotest at all, which would mean it can only run a single test at a time. You'd still be able to achieve a single thread by passing to `lit` (the driver) with `-j1`. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D65311/new/ https://reviews.llvm.org/D65311 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
