Zach, I think what would be idea is to have some way to tell the python file for a given test to build the binary for that test. In keeping with the minimalist philosophy for inline tests, it would be nice if this didn’t require any modification (or required only very minimal modification) to the testcase python file.
Sean > On Dec 12, 2014, at 3:35 PM, Zachary Turner <ztur...@google.com> wrote: > > lldb inline tests seem to generate their own Makefile and then clean it up > after they're done. lldb\test\lang\objc\objc-runtime-ivars seems to have a > Makefile checked into the repo. So when I run the test suite, it deletes > this repo and creates an annoyance every time I go to commit a changelist I'm > working on, because I have to remember to undo the fact that this file is > about to get deleted from the repo. > > What's the correct thing to do here? Should we: a) Remove this Makefile from > the repo and rely on the inline test to generate it, b) Only do something in > CleanMakefile() if BuildMakefile() was previously called? (this isn't the > case for me locally, since all of these tests are disabled on Windows, but > the cleanup isn't behind a similar check), c) some combinatino of the above? > > Would appreciate some assistance, as this is very annoying to keep having the > test suite modify my in-progress CLs. > _______________________________________________ > lldb-dev mailing list > lldb-dev@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
