<div dir="ltr">Yes, sure, thanks! </div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 19, 2017 at 4:55 PM, Reid Kleckner <span dir="ltr"><<a href="mailto:rnk@google.com" target="_blank">rnk@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Wed, Jul 19, 2017 at 3:27 PM, Davide Italiano <span dir="ltr"><<a href="mailto:davide@freebsd.org" target="_blank">davide@freebsd.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="m_-2077706390434123811gmail-">On Wed, Jul 19, 2017 at 3:12 PM,  <<a href="mailto:llvm.buildmaster@lab.llvm.org" target="_blank">llvm.buildmaster@lab.llvm.org</a><wbr>> wrote:<br>
> The Buildbot has detected a new failure on builder sanitizer-windows while building llvm.<br>
> Full details are available at:<br>
</span>>  <a href="http://lab.llvm.org:8011/builders/sanitizer-windows/builds/14405" rel="noreferrer" target="_blank">http://lab.llvm.org:8011/build<wbr>ers/sanitizer-windows/builds/<wbr>14405</a><br>
<span class="m_-2077706390434123811gmail-">><br>
> Buildbot URL: <a href="http://lab.llvm.org:8011/" rel="noreferrer" target="_blank">http://lab.llvm.org:8011/</a><br>
><br>
> Buildslave for this Build: sanitizer-windows<br>
><br>
> Build Reason: scheduler<br>
</span>> Build Source Stamp: [branch trunk] 308524<br>
> Blamelist: davide<br>
<span class="m_-2077706390434123811gmail-">><br>
> BUILD FAILED: failed run fuzzer tests<br>
><br>
> sincerely,<br>
>  -The Buildbot<br>
><br>
<br>
</span>This failure doesn't really seem related to any of my (recent)<br>
changes, but I may have overlooked, in which case, please let me know<br>
if there's something I can help with.<br></blockquote><div><br></div></span><div>This failure mode has happened twice in the last 100 builds:</div><div><a href="http://lab.llvm.org:8011/builders/sanitizer-windows/builds/14405/steps/run%20fuzzer%20tests/logs/stdio" target="_blank">http://lab.llvm.org:8011/<wbr>builders/sanitizer-windows/<wbr>builds/14405/steps/run%<wbr>20fuzzer%20tests/logs/stdio</a></div><div><a href="http://lab.llvm.org:8011/builders/sanitizer-windows/builds/14358/steps/run%20fuzzer%20tests/logs/stdio" target="_blank">http://lab.llvm.org:8011/<wbr>builders/sanitizer-windows/<wbr>builds/14358/steps/run%<wbr>20fuzzer%20tests/logs/stdio</a></div><div><br></div><div>We get a different OOM message than the one the test expects:</div><div><div>$ "FileCheck" "C:\b\slave\sanitizer-windows\<wbr>llvm\lib\Fuzzer\test\fuzzer-<wbr>oom.test" "--check-prefix=SINGLE_LARGE_<wbr>MALLOC"</div><div># command stderr:</div><div>C:\b\slave\sanitizer-windows\<wbr>llvm\lib\Fuzzer\test\fuzzer-<wbr>oom.test:8:22: error: expected string not found in input</div><div>SINGLE_LARGE_MALLOC: libFuzzer: out-of-memory (malloc(53{{.*}}))</div><div>                     ^</div><div><stdin>:1:1: note: scanning from here</div><div>INFO: Seed: 943780335</div><div>^</div><div><stdin>:10:17: note: possible intended match here</div><div>==1244== ERROR: libFuzzer: out-of-memory (used: 387Mb; limit: 300Mb)</div><div>                ^</div><div>error: command failed with exit status: 1</div></div><div><br></div><div>kcc, can I relax the FileCheck CHECK to make this less flaky? It's probably not worth digging in to find out why we get different messages.</div></div></div></div>
</blockquote></div><br></div>