search for: has_lld

...s_dir = "@LLVM_LIBS_DIR@" +config.llvm_shlib_dir = "@SHLIBDIR@" +config.llvm_plugin_ext = "@LLVM_PLUGIN_EXT@" +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") +config.host_triple = "@LLVM_HOST_TRIPLE@" +config.target_triple = "@TARGET_TRIPLE@" +config.host_arch = "@HOST_ARCH@" + +config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@" + + at LIT_SITE_CFG_I...

...+config.llvm_shlib_dir = "@SHLIBDIR@" >> +config.llvm_plugin_ext = "@LLVM_PLUGIN_EXT@" >> +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" >> +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" >> +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") >> +config.host_triple = "@LLVM_HOST_TRIPLE@" >> +config.target_triple = "@TARGET_TRIPLE@" >> +config.host_arch = "@HOST_ARCH@" >> + >> +config.llvm_use_sanitizer = "@LL...

...DIR@" > +config.llvm_shlib_dir = "@SHLIBDIR@" > +config.llvm_plugin_ext = "@LLVM_PLUGIN_EXT@" > +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" > +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" > +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") > +config.host_triple = "@LLVM_HOST_TRIPLE@" > +config.target_triple = "@TARGET_TRIPLE@" > +config.host_arch = "@HOST_ARCH@" > + > +config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@&qu...

I sorta enjoy debugging stuff like this, so if you don't mind, I'll dig into it once I get a chance -- traveling so, my access is a bit sketchy right now. I'll see if I can grab the logs and let you know if I find anything interesting. On Tue, Nov 21, 2017 at 7:04 PM, Zachary Turner <zturner at google.com> wrote: > That change was added specifically to workaround a failure