zturner added a comment. In https://reviews.llvm.org/D46005#1077000, @labath wrote:
> In https://reviews.llvm.org/D46005#1076978, @zturner wrote: > > > Does it print just the names of the .py files, or does it print the actual > > test classes and methods in the Class.TestName format, evaluate XFAIL and > > SKIPs, etc? > > > It prints everything: test file (including the relative path in the test > suite), test class name and test method name. > > It does not try to evaluate skips or xfails, but that was never the > intention. The idea is to feed this information to lit (as it needs to know > about the set of all tests), which can then run them with a bigger (smaller?) > granularity. The interpretation of the test results (skip,fail, ...) will > still be done by the lit test format, only now it could do it at a > test-method level instead of file-level. I thought the intention was going to be parallelize at file-granularity rather than method granularity, since the whole point of grouping tests together into classes is that they can share similar set up and tear down which may be expensive to perform multiple times. If we're going to parallelize at method-granularity, I would rather have one .py file per method. https://reviews.llvm.org/D46005 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
