After some investigation, it looks like the dotest.py is not returning non-zero exit codes for failures or errors in unittest2 tests. The dosep.py 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 dotest.py or if dosep.py was making a bad expectation. Either way, I'll track that down. dotest.py 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.
-Todd On Mon, Oct 13, 2014 at 4:19 PM, Todd Fiala <todd.fi...@gmail.com> wrote: > Hey all, > > It looks like dosep.py (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 dotest.py failure) correctly. > > I'm posting a bug on it now and will take it. > > -- > -Todd > -- -Todd
_______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
