[lldb-dev] lldb inline tests and Makefiles
zturner at google.com
Fri Dec 12 18:19:40 PST 2014
Agreed, but that's a difficult problem to solve given the current
architecture of the test suite. In my ideal world, we would just build all
the test executables at the same time we build lldb, and that would even
speed up the test suite, but i think we're a ways away from that.
On Fri, Dec 12, 2014 at 5:50 PM Jonathan Roelofs <jonathan at codesourcery.com>
> On 12/12/14 4:35 PM, Zachary Turner wrote:
> > lldb inline tests seem to generate their own Makefile and then clean it
> > 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
> > 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
> > on Windows, but the cleanup isn't behind a similar check), c) some
> > combinatino of the above?
> It would be extremely nice if building & testing didn't modify or create
> files in the directory checked out from svn/git. Having that makes it a
> easier to provide build reproducibility guarantees on shipped toolchains.
> > 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 at cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
> Jon Roelofs
> jonathan at codesourcery.com
> CodeSourcery / Mentor Embedded
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev