<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 14, 2019, at 11:26 AM, Adrian McCarthy via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">A recent change is causing several LLDB tests on Windows to fail and several more to time out, which I intend to look into.<div class=""><br class=""></div><div class="">It appears the timeout period is set to 600 seconds (10 minutes), which seems excessive and causes the Windows build bot to spend lots of time waiting. (e.g., <a href="http://lab.llvm.org:8011/builders/lldb-x64-windows-ninja/builds/7819/steps/test/logs/stdio" class="">http://lab.llvm.org:8011/builders/lldb-x64-windows-ninja/builds/7819/steps/test/logs/stdio</a>)</div><div class=""><br class=""></div><div class="">Is there a reason why the timeouts are set that long? What would be a reasonable value?</div></div></div></blockquote><br class=""></div><div>I recently increased/unified several internal timeouts throughout LLDB (<a href="https://reviews.llvm.org/D60340" class="">https://reviews.llvm.org/D60340</a>) in reaction to bots failing randomly on heavily used machines, particularly when ASAN is enabled, which can cause surprisingly long delays.</div><div><br class=""></div><div>Since the normal operation should be that no tests fail, waiting an extra 10 minutes in the exceptional case that a test does fail seems more desirable than the chance of a working test failing because of too-small timeout. Therefore, I'd rather pick an excessively large per-test timeout to be safe.</div><div><br class=""></div><div>-- adrian</div></body></html>