<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="">+Fred, +me<div class=""><br class=""></div><div class="">For LLDB tests: I believe this got much much better recently. Are you still seeing flaky LLDB tests? Any details you can share?</div><div class="">For sanitizer tests: I'm very much interesting in removing flakiness as well. Any specific tests you see as flaky?</div><div class=""><br class=""></div><div class="">Kuba<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 2, 2019, at 2:05 PM, Joel E. Denny via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hi David, Chandler,<br class=""></div><div class=""><br class=""></div><div class="">I see lldb tests hang often, and then I kill the dotest process.</div><div class=""><br class=""></div><div class="">I'd like to stop running check-all too, but I feel it's important when I modify FileCheck. The flakiness that Chandler mentioned makes it time-consuming to verify test results.</div><div class=""><br class=""></div><div class="">Joel<br class=""></div><div dir="ltr" class=""><div dir="ltr" class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, Jan 2, 2019 at 4:41 PM Chandler Carruth via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="">What you're seeing is just the fact that lit is waiting on subprocesses (select is waiting on the pipes i suspect).<div class=""><br class=""></div><div class="">Anyways, you'll need to dig into what it is waiting on, and what *that* process is doing that is stuck to make progress.</div><div class=""><br class=""></div><div class="">I've not seen anything like this, but I basically never run `check-all` these days because LLDB and sanitizer tests are too flaky. =[ I've not been able to interest anyone in fixing this either sadly.</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, Jan 2, 2019 at 10:09 AM David Greene via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br class="">
<br class="">
From time to time, I see check-all hang during running of lit tests.<br class="">
The hang always happens at the > 90% completion stage and I'm pretty<br class="">
sure all tests have been run and check-all is just waiting for<br class="">
lit/python to exit. I see a single python processing running, taking<br class="">
very little CPU time. An strace of that process shows this:<br class="">
<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 32168}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 1000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 2000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 4000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 8000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 16000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 32000}) = 0 (Timeout)<br class="">
futex(0x3bcc8c0, FUTEX_WAKE_PRIVATE, 1) = 1<br class="">
futex(0x3bcc8c0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, ffffffff) = 0<br class="">
futex(0x3bcc8c0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, ffffffff) = -1 EAGAIN (Resourc<br class="">
e temporarily unavailable) <br class="">
futex(0x3bcc8c0, FUTEX_WAKE_PRIVATE, 1) = 1<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
futex(0x3bcc8c0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, ffffffff) = -1 EAGAIN (Resourc<br class="">
e temporarily unavailable) <br class="">
futex(0x3bcc8c0, FUTEX_WAKE_PRIVATE, 1) = 1<br class="">
futex(0x3bcc8c0, FUTEX_WAKE_PRIVATE, 1) = 1<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)<br class="">
<br class="">
It appears that python is waiting for some I/O or something which never<br class="">
appears.<br class="">
<br class="">
Has anyone else seen this before? Any ideas of what is going on or how<br class="">
to fix it?<br class="">
<br class="">
-David<br class="">
_______________________________________________<br class="">
LLVM Developers mailing list<br class="">
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a><br class="">
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class="">
</blockquote></div>
_______________________________________________<br class="">
LLVM Developers mailing list<br class="">
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a><br class="">
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class="">
</blockquote></div></div>
</div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></div></body></html>