Hey all,

It looks like (used by ninja check-lldb) may not have transitioned from multithreaded to multiprocess module usage very well. I’m going to add some unit tests to it to verify it is capturing failed test runs and cores (wholesale failure) correctly.

I’m posting a bug on it now and will take it.

After some investigation, it looks like the is not returning non-zero exit codes for failures or errors in unittest2 tests. The script is expecting failures/errors to show up as non-zero return codes. I’m not sure if that’s a change in behavior in or if was making a bad expectation. Either way, I’ll track that down. really should be returning zero on all pass, unexpected successes, or xfails, but return something non-zero if there are any failures or errors at all.