<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 1, 2016, at 9:20 PM, Greg Parker <<a href="mailto:gparker@apple.com" class="">gparker@apple.com</a>> wrote:</div><div class=""><div class=""><br class=""><blockquote type="cite" class="">On Sep 1, 2016, at 9:06 PM, <a href="mailto:llvm.buildmaster@lab.llvm.org" class="">llvm.buildmaster@lab.llvm.org</a> wrote:<br class=""><br class="">The Buildbot has detected a new failure on builder sanitizer-x86_64-linux-fast while building llvm.<br class="">Full details are available at:<br class=""><a href="http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/16009" class="">http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/16009</a><br class=""><br class="">Buildbot URL: http://lab.llvm.org:8011/<br class=""><br class="">Buildslave for this Build: sanitizer-buildbot3<br class=""><br class="">Build Reason: scheduler<br class="">Build Source Stamp: [branch trunk] 280457<br class="">Blamelist: gparker,hfinkel<br class=""><br class="">BUILD FAILED: failed annotate failed check-llvm asan<br class=""><br class="">sincerely,<br class="">-The Buildbot<br class=""></blockquote><br class="">lit.py: /mnt/b/sanitizer-buildbot3/sanitizer-x86_64-linux-fast/build/llvm/utils/lit/lit/formats/googletest.py:39: error: unable to discover google-tests in '/mnt/b/sanitizer-buildbot3/sanitizer-x86_64-linux-fast/build/llvm_build_asan/unittests/MC/MCTests': Command '['/mnt/b/sanitizer-buildbot3/sanitizer-x86_64-linux-fast/build/llvm_build_asan/unittests/MC/MCTests', '--gtest_list_tests']' returned non-zero exit status 1<br class=""><br class="">This is a new lit error message introduced by r280455. I expect that the MCTests executable is hitting an asan error when run to report what tests it contains. Before r280455 the test silently passed as a result. Now the test fails. <br class=""><br class="">It's possible that the MCTests test has been failing to run in this configuration for a long time. I don't think the buildbot logs for previous builds are detailed enough to say whether MCTests was running or not.<br class=""><br class="">I'll try to reproduce locally.</div></div></blockquote><br class=""></div><div>Didn't reproduce on my OS X asan build.</div><div><br class=""></div><div>This is probably an old bug in the unittests/MC test code or possibly in the code that it is testing. I recommend disabling unittests/MC on asan configurations until it can be investigated, but I don't know how to do that. Other options are to disable unittests/MC unconditionally, or roll back r280455 until unittests/MC can be fixed.</div><div><br class=""></div><div>Is there someone who can reproduce this who can take it over?</div><div><br class=""></div><div><br class=""></div><div>-- </div><div>Greg Parker <a href="mailto:gparker@apple.com" class="">gparker@apple.com</a> Runtime Wrangler</div><div><br class=""></div><div><br class=""></div></body></html>