zturner added a comment. In https://reviews.llvm.org/D54567#1300031, @stella.stamenova wrote:
> In https://reviews.llvm.org/D54567#1300030, @aprantl wrote: > > > In https://reviews.llvm.org/D54567#1300000, @zturner wrote: > > > > > http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-clang-5.0.2/ > > > > > > What do I need to click on to get the equivalent of this: > > > http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/31244/steps/test6/logs/stdio > > > > > > Click on a recent build and then on "Console Output". Here is one from > > yesterday (we are upgrading the machines right now and temporarily broke > > the build): > > > > http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-clang-5.0.2/1356/consoleFull > > > Ok, now I see it: > > python /opt/llvm/zorg/zorg/jenkins//build.py --assertions > --cmake-type=Release --cmake-flag=-DLLVM_TARGETS_TO_BUILD=X86 > --cmake-flag=-DLLDB_TEST_USE_CUSTOM_C_COMPILER=On > --cmake-flag=-DLLDB_TEST_USE_CUSTOM_CXX_COMPILER=On > --cmake-flag=-DLLDB_TEST_C_COMPILER=/Users/buildslave/jenkins/workspace/lldb-cmake-clang-5.0.2/lldb-build/history/clang-5.0.2/bin/clang > > --cmake-flag=-DLLDB_TEST_CXX_COMPILER=/Users/buildslave/jenkins/workspace/lldb-cmake-clang-5.0.2/lldb-build/history/clang-5.0.2/bin/clang++ > --dotest-flag=--skip-category --dotest-flag=gmodules lldb-cmake > The equivalent command line after this patch would be to keep all of the `-DLLDB_TEST_XXX` variables, but to add one more that says `-DLLDB_LIT_TOOLS_DIR=/Users/buildslave/jenkins/workspace/lldb-cmake-clang-5.0.2/lldb-build/history/clang-5.0.2/bin`. It will search this path first when looking for `clang` and `clang++` for all of the LLDB tests, but still use the `_CXX_COMPILER` and `_C_COMPILER` paths for the `LLDB-Suite` tests. At least, that's the intention. https://reviews.llvm.org/D54567 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
