<div dir="ltr"><div>I have a windows box, I'll take a look.</div>fuzzer looks like a flake, I started rebuild on the same revision <a href="http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer/builds/39189">http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer/builds/39189</a><div><br><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 17 Sep 2020 at 21:25, Teresa Johnson via Phabricator <<a href="mailto:reviews@reviews.llvm.org">reviews@reviews.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">tejohnson added a comment.<br>
<br>
I had to revert due to 2 bot failures.<br>
<br>
<a href="http://lab.llvm.org:8011/builders/sanitizer-windows/builds/69871/steps/stage%201%20check/logs/stdio" rel="noreferrer" target="_blank">http://lab.llvm.org:8011/builders/sanitizer-windows/builds/69871/steps/stage%201%20check/logs/stdio</a><br>
<br>
This one is in my new test. @vitalybuka can you think of why this might failure on Windows? It looks like the call to StackDepotPrintAll() is failing early as there is no output reported from it. Perhaps it is having trouble symbolizing the bogus stack addresses?<br>
<br>
<a href="http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer/builds/39187/steps/check-fuzzer/logs/stdio" rel="noreferrer" target="_blank">http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer/builds/39187/steps/check-fuzzer/logs/stdio</a><br>
<br>
@vitalybuka: This one seems completely unrelated to my change. Does it have flaky failures sometimes?<br>
<br>
<br>
Repository:<br>
  rG LLVM Github Monorepo<br>
<br>
CHANGES SINCE LAST ACTION<br>
  <a href="https://reviews.llvm.org/D87792/new/" rel="noreferrer" target="_blank">https://reviews.llvm.org/D87792/new/</a><br>
<br>
<a href="https://reviews.llvm.org/D87792" rel="noreferrer" target="_blank">https://reviews.llvm.org/D87792</a><br>
<br>
</blockquote></div>