I have some ideas for how to run the different variants as separate tests, but I'll save it for the next RFC :)
On Wed, Apr 4, 2018 at 10:24 AM Jonas Devlieghere <jdevliegh...@apple.com> wrote: > > > On Apr 4, 2018, at 5:12 PM, Adrian Prantl <apra...@apple.com> wrote: > > > > > > > >> On Apr 4, 2018, at 9:07 AM, Zachary Turner <ztur...@google.com> wrote: > >> > >> Sure, but getting lit to run one file at a time is a nice incremental > step towards that and can make both patches easier to review. > > > > Agreed, I just want to make sure that we are all on the same page as to > which direction we want to evolve the code to. > > Preferably lit would take care of as much as possible. I think Zachary’s > idea makes sense as an incremental step. If we think of one python file as > a google test executable, it makes sense to return a list of test for every > python file for “v2”. I think running the different variants as separate > tests is going to be “v3” and will require quite a bit more work. > > > > > -- adrian > >
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
