<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">-llvm-dev + lldb-dev for the lldv test failures.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 3, 2019, at 7:33 AM, Joel E. Denny <<a href="mailto:jdenny.ornl@gmail.com" class="">jdenny.ornl@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">All,</div><div class=""><br class=""></div><div class="">Thanks for the replies. Kuba: For LLDB, when were things expected to have improved? It's possible things improved for me at some point, but this isn't something I've found time to track carefully, and I still see problems. <br class=""></div><div class=""><br class=""></div><div class="">I ran check-all a couple of times last night at r350238, which I pulled yesterday. Here are the results:</div><div class=""><br class=""></div><div class="">```</div><div class="">********************<br class="">Testing Time: 5043.24s<br class="">********************<br class="">Unexpected Passing Tests (2):<br class=""> lldb-Suite :: functionalities/asan/TestMemoryHistory.py<br class=""> lldb-Suite :: functionalities/asan/TestReportData.py<br class=""><br class="">********************<br class="">Failing Tests (54):<br class=""> Clang :: CXX/modules-ts/basic/<a href="http://basic.link/p2/module.cpp" class="">basic.link/p2/module.cpp</a><br class=""> Clang :: Modules/ExtDebugInfo.cpp<br class=""> Clang :: Modules/using-directive-redecl.cpp<br class=""> Clang :: Modules/using-directive.cpp<br class=""> Clang :: PCH/chain-late-anonymous-namespace.cpp<br class=""> Clang :: PCH/cxx-namespaces.cpp<br class=""> Clang :: PCH/namespaces.cpp<br class=""> LLDB :: ExecControl/StopHook/stop-hook-threads.test<br class=""> LeakSanitizer-AddressSanitizer-x86_64 :: TestCases/Linux/<a href="http://use_tls_dynamic.cc" class="">use_tls_dynamic.cc</a><br class=""> LeakSanitizer-Standalone-x86_64 :: TestCases/Linux/<a href="http://use_tls_dynamic.cc" class="">use_tls_dynamic.cc</a><br class=""> MemorySanitizer-X86_64 :: dtls_test.c<br class=""> MemorySanitizer-lld-X86_64 :: dtls_test.c<br class=""> lldb-Suite :: functionalities/register/register_command/TestRegisters.py<br class=""> lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py<br class=""></div></div></div></div></div></div></div></div></div></div></blockquote><div><br class=""></div><div>It’s hard to diagnose dotest failures without the log. </div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestBorrowedReferences<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestDictionaryResolutionWithDot<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestExtractingUInt64ThroughStructuredData<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestGlobalNameResolutionNoDot<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestGlobalNameResolutionWithDot<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestInstanceNameResolutionNoDot<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestModuleNameResolutionNoDot<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestObjectAttributes<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestOwnedReferences<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonByteArray<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonBytes<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonCallableCheck<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonCallableInvoke<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonDictionaryManipulation<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonDictionaryToStructuredDictionary<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonDictionaryValueEquality<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonFile<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonInteger<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonIntegerToStr<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonIntegerToStructuredInteger<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonListManipulation<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonListToStructuredList<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonListValueEquality<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonString<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonStringToStr<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonStringToStructuredString<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonTupleInitializerList<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonTupleInitializerList2<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonTupleSize<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonTupleToStructuredList<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonTupleValues<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestResetting<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestTypeNameResolutionNoDot<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonExceptionStateTest.TestAcquisitionSemantics<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonExceptionStateTest.TestAutoRestoreChanged<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonExceptionStateTest.TestAutoRestoreSemantics<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonExceptionStateTest.TestDiscardSemantics<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonExceptionStateTest.TestExceptionStateChecking<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonExceptionStateTest.TestManualRestoreSemantics<br class=""> lldb-Unit :: ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonExceptionStateTest.TestResetSemantics<br class=""></div></div></div></div></div></div></div></div></div></div></blockquote><div><br class=""></div><div>Those unit test failures don’t ring a bell. Anyone’s seen this? Here too, knowing exactly the error message would help.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""> Expected Passes : 57489<br class=""> Expected Failures : 276<br class=""> Unsupported Tests : 1883<br class=""> Unexpected Passes : 2<br class=""> Unexpected Failures: 54<br class=""><br class="">14 warning(s) in tests.<br class="">FAILED: CMakeFiles/check-all<br class="">```</div><div class=""><br class=""></div><div class="">I immediately ran it again and saw one new unexpected fail:</div><div class=""><br class=""></div><div class="">```</div><div class=""> lldb-Suite :: tools/lldb-mi/syntax/TestMiSyntax.py<br class="">```</div></div></div></div></div></div></div></div></div></div></blockquote><div><br class=""></div><div>Adrian, do we have remaining flakiness in the MI tests? Is this one of the GSoc tests?</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">and one new unresolved test:</div><div class=""><br class=""></div><div class="">```</div><div class=""> lldb-Suite :: tools/lldb-vscode/breakpoint/TestVSCode_setBreakpoints.py</div><div class="">```</div><div class=""><br class=""></div><div class="">On the second run but not the first, it hung all night long waiting for TestVSCode_setBreakpoints.py to terminate. I killed dotest.py to get the final results.</div></div></div></div></div></div></div></div></div></div></blockquote><div><br class=""></div><div>We have disabled the VScode tests on Darwin because they very flaky on the bots. +Greg who added those.</div><div><br class=""></div><div>Fred</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">I currently clone <<a href="https://github.com/llvm-project/llvm-project-20170507" class="">https://github.com/llvm-project/llvm-project-20170507</a>>. I configure with `BUILD_SHARED_LIBS=true` and `-DLLVM_ENABLE_PROJECTS='clang;openmp;libcxx;libcxxabi;lldb;compiler-rt;lld;polly'`, among other options. I have to run check-all with LD_LIBRARY_PATH pointing at my build's lib directory, or there are many more LLDB failures. I believe that's not true for most test suites. I'm building and testing under Ubuntu 18.04.1.<br class=""></div><div class=""><br class=""></div><div class="">Hope that helps. I'm happy to provide more details. Just tell me where you'd like to start.<br class=""></div><div class=""><br class=""></div><div class="">Thanks.</div><div class=""><br class=""></div><div class="">Joel<br class=""></div><div class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, Jan 2, 2019 at 5:51 PM Kuba Mracek <<a href="mailto:mracek@apple.com" class="">mracek@apple.com</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 style="overflow-wrap: break-word;" 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 class=""><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" target="_blank" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="gmail-m_-8898860875678207941Apple-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" target="_blank" class="">llvm-dev@lists.llvm.org</a><br class=""><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class=""></div></blockquote></div><br class=""></div></div></blockquote></div></div></div></div></div></div></div></div></div>
</div></blockquote></div><br class=""></body></html>