Re: [lldb-dev] [llvm-dev] [lit] check-all hanging

[Frédéric Riss via lldb-dev]

-llvm-dev + lldb-dev for the lldv test failures.

> On Jan 3, 2019, at 7:33 AM, Joel E. Denny  wrote:
> 
> All,
> 
> 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. 
> 
> I ran check-all a couple of times last night at r350238, which I pulled 
> yesterday.  Here are the results:
> 
> ```
> 
> Testing Time: 5043.24s
> 
> Unexpected Passing Tests (2):
> lldb-Suite :: functionalities/asan/TestMemoryHistory.py
> lldb-Suite :: functionalities/asan/TestReportData.py
> 
> 
> Failing Tests (54):
> Clang :: CXX/modules-ts/basic/basic.link/p2/module.cpp
> Clang :: Modules/ExtDebugInfo.cpp
> Clang :: Modules/using-directive-redecl.cpp
> Clang :: Modules/using-directive.cpp
> Clang :: PCH/chain-late-anonymous-namespace.cpp
> Clang :: PCH/cxx-namespaces.cpp
> Clang :: PCH/namespaces.cpp
> LLDB :: ExecControl/StopHook/stop-hook-threads.test
> LeakSanitizer-AddressSanitizer-x86_64 :: 
> TestCases/Linux/use_tls_dynamic.cc
> LeakSanitizer-Standalone-x86_64 :: TestCases/Linux/use_tls_dynamic.cc
> MemorySanitizer-X86_64 :: dtls_test.c
> MemorySanitizer-lld-X86_64 :: dtls_test.c
> lldb-Suite :: functionalities/register/register_command/TestRegisters.py
> lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py

It’s hard to diagnose dotest failures without the log. 

> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestBorrowedReferences
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestDictionaryResolutionWithDot
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestExtractingUInt64ThroughStructuredData
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestGlobalNameResolutionNoDot
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestGlobalNameResolutionWithDot
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestInstanceNameResolutionNoDot
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestModuleNameResolutionNoDot
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestObjectAttributes
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestOwnedReferences
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonByteArray
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonBytes
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonCallableCheck
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonCallableInvoke
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonDictionaryManipulation
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonDictionaryToStructuredDictionary
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonDictionaryValueEquality
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonFile
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonInteger
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonIntegerToStr
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonIntegerToStructuredInteger
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonListManipulation
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonListToStructuredList
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonListValueEquality
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonString
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonStringToStr
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPythonStringToStructuredString
> lldb-Unit :: 
> ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestPytho

Re: [lldb-dev] [llvm-dev] [lit] check-all hanging

[Adrian Prantl via lldb-dev]

> On Jan 3, 2019, at 8:30 AM, Frédéric Riss  wrote:
> 
> -llvm-dev + lldb-dev for the lldv test failures.
> 
>> On Jan 3, 2019, at 7:33 AM, Joel E. Denny > > wrote:
> 
>>   Expected Passes: 57489
>>   Expected Failures  : 276
>>   Unsupported Tests  : 1883
>>   Unexpected Passes  : 2
>>   Unexpected Failures: 54
>> 
>> 14 warning(s) in tests.
>> FAILED: CMakeFiles/check-all
>> ```
>> 
>> I immediately ran it again and saw one new unexpected fail:
>> 
>> ```
>> lldb-Suite :: tools/lldb-mi/syntax/TestMiSyntax.py
>> ```
> 
> Adrian, do we have remaining flakiness in the MI tests? Is this one of the 
> GSoc tests?

That particular test still uses pexpect and needs to be rewritten as a 
LIT-based test; so, yes.

-- adrian
> 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [lit] check-all hanging

[Jan Kratochvil via lldb-dev]

On Thu, 03 Jan 2019 23:47:59 +0100, Adrian Prantl via lldb-dev wrote:
> > On Jan 3, 2019, at 8:30 AM, Frédéric Riss  wrote:
> >> I immediately ran it again and saw one new unexpected fail:
> >> lldb-Suite :: tools/lldb-mi/syntax/TestMiSyntax.py
> > 
> > Adrian, do we have remaining flakiness in the MI tests? Is this one of the 
> > GSoc tests?
> 
> That particular test still uses pexpect and needs to be rewritten as a 
> LIT-based test; so, yes.

TestMiSyntax was the only test failing for me with /usr/lib/debug debuginfos
installed on Linux and Joel may be running a Linux platform according to some
of his mails.

I have now checked in a fix which may remove this false FAIL:
https://reviews.llvm.org/D55859 symbols.enable-external-lookup=false on all 
hosts (not just OSX)


Jan
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev