tfiala added a comment. Okay I just looked at those, Pavel.
They fall into a category that I know is not yet handled. This is the category: - No test method is "open" (i.e. the dotest.py inferior is not in between a start_test/end_test) when the timeout occurs. Thus, we cannot "charge" the timeout to a test method. Thus, it gets charged to the file. - When we rerun, we currently do not clear file-level results. (We should right before the rerun). This hadn't been prioritized because I haven't in practice run into timeouts that are occurring outside of a test method. That implies either the startup or the shutdown of the python dotest.py inferior is hanging if you are consistently hitting that. That in itself is an interesting event to investigate. I'll file a bug on this since there is a reasonable solution that will solve this one. I'll get a bug tracking that once I finish writing this. http://reviews.llvm.org/D19214 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
