[Lldb-commits] [lldb] r339911 - Add a new tool named "lldb-vscode" that implements the Visual Studio Code Debug Adaptor Protocol

[Adrian Prantl via lldb-commits]

On Aug 17, 2018, at 1:44 PM, Greg Clayton <clayborg at gmail.com> wrote:

> I run everything on a mac and there are no failures on my machine. 
> Can you find out exactly how the test suite is invoked so I can try to reproduce?

You can find the exact invocation in the build logs:

cmake /Users/buildslave/jenkins/workspace/lldb-cmake/src/llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_INSTALL_PREFIX=/Users/buildslave/jenkins/workspace/lldb-cmake/results/lldb '-DLLDB_TEST_USER_ARGS=--arch;x86_64;--build-dir;/Users/buildslave/jenkins/workspace/lldb-cmake/build/lldb-test-build.noindex;--session-file-format;fm;-s=/Users/buildslave/jenkins/workspace/lldb-cmake/test/logs;--rerun-all-issues;--env;TERM=vt100' '-DLLVM_LIT_ARGS=--xunit-xml-output=/Users/buildslave/jenkins/workspace/lldb-cmake/test/results.xml -v' -G Ninja

ninja

env TERM=vt100 ninja -v check-lldb

This is running on a 2013 Mac Pro with 24 threads on 10.13.5 with Xcode 9.2.

-- adrian


> 
>> On Aug 17, 2018, at 1:39 PM, Adrian Prantl <aprantl at apple.com> wrote:
>> 
>> Here's a third failure:
>> 
>> http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/9021/console
>> 
>> ======================================================================
>> FAIL: test_commands (TestVSCode_launch.TestVSCode_launch)
>> ----------------------------------------------------------------------
>> Traceback (most recent call last):
>> File "/Users/buildslave/jenkins/workspace/lldb-cmake/src/llvm/tools/lldb/packages/Python/lldbsuite/test/decorators.py", line 341, in wrapper
>>   return func(self, *args, **kwargs)
>> File "/Users/buildslave/jenkins/workspace/lldb-cmake/src/llvm/tools/lldb/packages/Python/lldbsuite/test/tools/lldb-vscode/launch/TestVSCode_launch.py", line 317, in test_commands
>>   self.verify_commands('stopCommands', output, stopCommands)
>> File "/Users/buildslave/jenkins/workspace/lldb-cmake/src/llvm/tools/lldb/packages/Python/lldbsuite/test/tools/lldb-vscode/lldbvscode_testcase.py", line 115, in verify_commands
>>   cmd, flavor))
>> AssertionError: False is not True : verify 'frame variable' found in console output for 'stopCommands'
>> Config=x86_64-/Users/buildslave/jenkins/workspace/lldb-cmake/build/bin/clang-8
>> ----------------------------------------------------------------------
>> Ran 11 tests in 13.143s
>> 
>> RESULT: FAILED (10 passes, 1 failures, 0 errors, 0 skipped, 0 expected failures, 0 unexpected successes)
>> 
>> Do you have access to a Mac to reproduce these failures?
>> 
>> -- adrian
>> 
>>> On Aug 17, 2018, at 11:33 AM, Adrian Prantl <aprantl at apple.com> wrote:
>>> 
>>> Here's the output from attach:
>>> 
>>> http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/9017/testReport/lldb-Suite/tools_lldb-vscode_attach/TestVSCode_attach_py
>>> 
>>>> On Aug 17, 2018, at 11:32 AM, Adrian Prantl via lldb-commits <lldb-commits at lists.llvm.org> wrote:
>>>> 
>>>> 
>>>> 
>>>>> On Aug 17, 2018, at 10:35 AM, Greg Clayton <clayborg at gmail.com> wrote:
>>>>> 
>>>>> I can expectedFail this test if needed?
>>>> 
>>>> I'm afraid it looks like that won't be good enough. I just had to manually log into the build node and kill TestVSCode_variables.py, too, because it was hanging indefinitely. We either need to figure out what is going with these tests or skip them on Darwin entirely. 
>>>> 
>>>> -- adrian
>>>> 
>>>> _______________________________________________
>>>> lldb-commits mailing list
>>>> lldb-commits at lists.llvm.org
>>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
>>> 
>> 
>