If you dont’ care about running debuginfo-tests, and don’t maintain a bot that runs debuginfo-tests, you can stop reading.
I’ve uploaded a patch [https://reviews.llvm.org/D39605] that changes the way you run debuginfo-tests.
Prior to this patch, the way to run them is to clone an external git repository into clang/test and then debuginfo-tests will happen transparently when you run “ninja check-clang”.
After this patch, there will be two workflows depending on if you use multi-repo or mono-repo.
multi-repo: You will need to clone debuginfo-tests into llvm/projects, then run “ninja check-debuginfo”
mono-repo: pass -DLLVM_ENABLE_PROJECTS=“debuginfo-tests”, then run “ninja check-debuginfo”
The motivation for this change is that planned additions to debuginfo-tests require us to be able to make use of lld, and as a result the tests need to live somewhere that can access both clang and lld, not just clang. Furthermore, giving them their own target “check-debuginfo” as opposed to being transparently added to check-clang makes more sense from a usability perspective. Finally, this new approach is mono-repo friendly whereas the previous one was not.
I’m hoping this won’t be too disturbing of a change, but please leave comments and issues on this thread or on the code rview.