I think we don't. If we consider them stable enough for enabling them on a buildbot AND we agree to revert changes breaking the unittests then I am happy with enabling them (doing it should take very little effort from our side). Otherwise I would prefer to wait until we can get them to a stable state.
On Mon, Apr 4, 2016 at 10:53 PM Todd Fiala <todd.fi...@gmail.com> wrote: > One more update: > > The Green Dragon OS X LLDB builder now actually runs the gtests instead of > just building them. > > The gtests run as a phase right before the Python test suite. A non-zero > value returning from the gtests will cause the OS X LLDB build to fail. > Right now, tracking down the cause of the failure will require looking at > the console log for the build and test job. I'm excited to see our gtest > test count has gone from roughly 17 to over 100 now! > > Pavel or Tamas, are we running the gtests on the Linux buildbots? > > -Todd > > On Mon, Apr 4, 2016 at 10:49 AM, Todd Fiala <todd.fi...@gmail.com> wrote: > >> Hi all, >> >> I've made a minor change to the Green Dragon LLDB OS X Xcode build >> located here: >> http://lab.llvm.org:8080/green/job/LLDB/ >> >> 1. Previously, the python test run used the default C/C++ compiler to >> build test inferiors. Now it uses the just-built clang/clang++ to build >> test inferiors. At some point in the future, we will change this to a >> matrix of important clang/clang++ versions (e.g. some number of official >> Xcode-released clangs). For now, however, we'll continue to build with >> just one, and that one will be the one in the clang build tree. >> >> 2. The Xcode llvm/clang build step now includes compiler-rt and libcxx. >> This, together with the change above, will allow the newer LLDB TSAN tests >> to run. >> >> If you're ever curious how the Xcode build is run, it uses the build.py >> script in the zorg repo (http://llvm.org/svn/llvm-project/zorg/trunk) >> under zorg/jenkins/build.py. The build constructs the build tree with a >> "derive-lldb" command, and does the Xcode build with the "lldb" command. >> >> Please let me know if you have any questions. >> >> I'll address any hiccups that may show up ASAP. >> >> Thanks! >> -- >> -Todd >> > > > > -- > -Todd >
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
