dzhidzhoev wrote: > Ok I see what `LLDB_SHELL_TESTS_DISABLE_REMOTE` does but I don't get why. > Perhaps you can show how a developer would: > > * Hit the problem that this option addresses > * Apply the option > * What problems it would solve and what that final build looks like > * What the value of the results of that build are to the developer
For example: 1. A developer uses gcc to cross-compile lldb and run remote testing. 2. API tests pass because Makefile.rules provides the ability to use different compilers/adjusts all necessary flags. 3. Shell tests fail for some reason (--sysroot is not enough or not provided/some tests use clang-specific flags/etc). The developer thinks that it's sufficient for them to get away with Shell tests running only for the host platform. 4. LLDB_SHELL_TESTS_DISABLE_REMOTE is set to on. 5. Shell tests are compiled and run locally => tests are green. https://github.com/llvm/llvm-project/pull/95986 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
