Regression
Test Clang 7.0.1 / lldb-Suite.functionalities/data-formatter/stringprinter.TestStringPrinter.py (from lldb-Suite)
Failing for the past 1 build
(Since
#270 )

Stacktrace
lldb version 10.0.99 (http://labmaster3.local/git/llvm-project.git revision 1a3dd638c4a9173e53628b497a1aadc31c32eb50) clang revision daa79c5338228a746a7eba0cf2f2f356e1d45a5b llvm revision daa79c5338228a746a7eba0cf2f2f356e1d45a5b LLDB library dir: /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/bin LLDB import library dir: /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/bin libstdcxx tests will not be run because: Don't know how to build with libstdcxx on macosx Skipping following debug info categories: ['dwo'] Session logs for test failures/errors/unexpected successes will go into directory '/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/test/logs' Command invoked: /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/test/dotest.py --arch=x86_64 -s /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/lldb-test-traces -S nm -u CXXFLAGS -u CFLAGS --executable /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/./bin/lldb --dsymutil /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/./bin/dsymutil --filecheck /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/./bin/FileCheck -C /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/clang_701_build/bin/clang --codesign-identity lldb_codesign --server /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/./bin/debugserver --arch x86_64 --build-dir /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/lldb-test-build.noindex -s=/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/test/logs -t --env TERM=vt100 --skip-category gmodules --skip-category watchpoint --arch=x86_64 --env LLVM_LIBS_DIR=/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/./lib --build-dir /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/tools/lldb/lldb-test-build.noindex --module-cache-dir /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/tools/lldb/lldb-test-build.noindex/module-cache-lldb /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/packages/Python/lldbsuite/test/functionalities/data-formatter/stringprinter -p TestStringPrinter.py Change dir to: /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/packages/Python/lldbsuite/test/functionalities/data-formatter/stringprinter runCmd: settings set symbols.enable-external-lookup false output: runCmd: settings set plugin.process.gdb-remote.packet-timeout 60 output: runCmd: settings set symbols.clang-modules-cache-path "/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/tools/lldb/lldb-test-build.noindex/module-cache-lldb" output: runCmd: settings set use-color false output: Adding tearDown hook: <function <lambda> at 0x105d70c80> runCmd: frame variable output: (int) argc = 1 (const char **) argv = 0x00007ffeecf45ce0 (std::__1::string) stdstring = "Hello\t\tWorld\nI am here\t\tto say hello\n" (const char *) constcharstar = 0x00007fbbe9e00080 "Hello\t\tWorld\nI am here\t\tto say hello\n" (std::__1::string) longstring = "I am a very long string; in fact I am longer than any reasonable length that a string should be; quite long indeed; oh my, so many words; so many letters; this is kind of like writing a poem; except in real life all that is happening is just me producing a very very long set of words; there is text here, text there, text everywhere; it fills me with glee to see so much text; all around me it's just letters, and symbols, and other pleasant drawings that cause me a large amount of joy upon visually seeing them with my eyes; well, this is now a lot of letters, but it is still not enough for the purpose of the test I want to test, so maybe I should copy and paste this a few times, you know.. for science, or somethingI am a very long string; in fact I am longer than any reasonable length that a string should be; quite long indeed; oh my, so many words; so many letters; this is kind of like writing a poem; except in real life all that is happening is just me producing a very very long set of words; there is text he"... (const char *) longconstcharstar = 0x00007fbbea800000 "I am a very long string; in fact I am longer than any reasonable length that a string should be; quite long indeed; oh my, so many words; so many letters; this is kind of like writing a poem; except in real life all that is happening is just me producing a very very long set of words; there is text here, text there, text everywhere; it fills me with glee to see so much text; all around me it's just letters, and symbols, and other pleasant drawings that cause me a large amount of joy upon visually seeing them with my eyes; well, this is now a lot of letters, but it is still not enough for the purpose of the test I want to test, so maybe I should copy and paste this a few times, you know.. for science, or somethingI am a very long string; in fact I am longer than any reasonable length that a string should be; quite long indeed; oh my, so many words; so many letters; this is kind of like writing a poem; except in real life all that is happening is just me producing a very very long set of words; there is text he"... runCmd: setting set escape-non-printables false output: <bound method SBProcess.Kill of <lldb.SBProcess; proxy of <Swig Object of type 'lldb::SBProcess *' at 0x105d6e270> >>: success Executing tearDown hook: <function <lambda> at 0x105d70c80> runCmd: setting set escape-non-printables true output: PASS: LLDB (/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/clang_701_build/bin/clang-7-x86_64) :: test_dsym (lldbsuite.test.lldbtest.TestStringPrinter) runCmd: settings set symbols.enable-external-lookup false output: runCmd: settings set plugin.process.gdb-remote.packet-timeout 60 output: runCmd: settings set symbols.clang-modules-cache-path "/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/tools/lldb/lldb-test-build.noindex/module-cache-lldb" output: runCmd: settings set use-color false output: FAIL: LLDB (/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/clang_701_build/bin/clang-7-x86_64) :: test_dwarf (lldbsuite.test.lldbtest.TestStringPrinter) <bound method SBProcess.Kill of <lldb.SBProcess; proxy of <Swig Object of type 'lldb::SBProcess *' at 0x105c03e10> >>: success UNSUPPORTED: LLDB (/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/clang_701_build/bin/clang-7-x86_64) :: test_dwo (lldbsuite.test.lldbtest.TestStringPrinter) (test case does not fall in any category of interest for this run) UNSUPPORTED: LLDB (/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/clang_701_build/bin/clang-7-x86_64) :: test_gmodules (lldbsuite.test.lldbtest.TestStringPrinter) (test case does not fall in any category of interest for this run) Restore dir to: /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/tools/lldb/lit ====================================================================== FAIL: test_dwarf (lldbsuite.test.lldbtest.TestStringPrinter) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 1748, in test_method return attrvalue(self) File "/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/packages/Python/lldbsuite/test/decorators.py", line 111, in wrapper func(*args, **kwargs) File "/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/packages/Python/lldbsuite/test/lldbinline.py", line 124, in _test self.do_test() File "/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/packages/Python/lldbsuite/test/lldbinline.py", line 151, in do_test "inline test did not hit a single breakpoint") AssertionError: False is not True : inline test did not hit a single breakpoint Config=x86_64-/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/clang_701_build/bin/clang-7 ---------------------------------------------------------------------- Ran 4 tests in 3.632s RESULT: FAILED (1 passes, 1 failures, 0 errors, 2 skipped, 0 expected failures, 0 unexpected successes)