[PATCH] D68708: [RFC] Adopt Dexter and use it to run debuginfo-tests

[Jeremy Morse via Phabricator via llvm-commits]

jmorse added a comment.

The lldb-cmake pipeline is now running those internal tests successfully with 7f738c811ac4 <https://reviews.llvm.org/rG7f738c811ac434fc70658cd5ed39b9a36605b561>, which is great. I'll enable a few of the 'dexter-tests' tests for darwin and see how that goes.

I'm a bit worried about this [1] green-dragon pipeline -- it started failing when dexter landed, with this message:

  cd /Users/buildslave/jenkins/workspace/clang-stage1-RA/llvm-project/clang/bindings/python && /usr/local/Cellar/cmake/3.12.4/bin/cmake -E env CLANG_LIBRARY_PATH=/Users/buildslave/jenkins/workspace/clang-stage1-RA/clang-build/lib -m unittest discover
  cmake -E env: unknown option '-m'

In previous runs a path to a python executable appeared in that command; it's probably not appearing now because I'm unsetting PYTHON_EXECUTABLE after finding python3, similar to Reids problem in D69684 <https://reviews.llvm.org/D69684>. It's not clear to me what the solution may be -- possibly running FindPythonInterp after unsetting, or save/restoring the configuration instead of wiping it? How CMake files interact with each other isn't my area of expertise, alas.

[0] http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/
[1] http://green.lab.llvm.org/green/job/clang-stage1-RA/


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D68708/new/

https://reviews.llvm.org/D68708