Hey Dawn, For what its worth, if you're attempting to test a cmake-based MacOSX build, I have yet to get that to ever work. There is a bunch of bundling and code signing operations that occur that don't (AFAICT) happen in the cmake build. And so the tests can pick up the wrong frameworks and whatnot. If your line above does indeed look like it's working, it might be worth taking a quick peek at one of the running tests to make sure it is really loading all the write dynamic bits (i.e. ensure you're not getting some kind of frankenstein test setup where you're using exes from your build but system-wide/xcode frameworks or something).
(And if you did find a way that works with ninja check-lldb, that's awesome!) -Todd On Wed, Oct 1, 2014 at 9:49 PM, <d...@burble.org> wrote: > Thanks Sean! From this I was able to figure out that I could test > the cmake+ninja build with: > ./dotest.py -v --executable <builddir>/bin/lldb > Which I think tested things correctly, did it? At least the failure > counts were close when compared to the XCode built lldb results. > > Thanks! > -Dawn > > On Wed, Oct 01, 2014 at 06:04:25PM -0700, Sean Callanan wrote: > > Dawn, > > > > ninja check-lldb isn???t the way we typically run the test suite on Mac > OS. > > The way we do it is by running > > > > ./dotest.py -v > > > > in the test/ subdirectory. The IDE ???Run Tests??? action does (as you > surmised) nothing in our project. > > > > Sean > _______________________________________________ > lldb-dev mailing list > lldb-dev@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > -- Todd Fiala | Software Engineer | tfi...@google.com
_______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
