Jenkins is going to shut down

Regression

Test Clang 7.0.1 / lldb-Suite.functionalities/thread/concurrent_events.TestConcurrentDelaySignalBreak.py (from lldb-Suite)

Failing for the past 1 build (Since Unstable#270 )
Took 2.9 sec.

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/thread/concurrent_events -p TestConcurrentDelaySignalBreak.py
Change dir to: /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/packages/Python/lldbsuite/test/functionalities/thread/concurrent_events
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: 

runCmd: file /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/tools/lldb/lldb-test-build.noindex/functionalities/thread/concurrent_events/TestConcurrentDelaySignalBreak.test/a.out
output: Current executable set to '/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/tools/lldb/lldb-test-build.noindex/functionalities/thread/concurrent_events/TestConcurrentDelaySignalBreak.test/a.out' (x86_64).


runCmd: breakpoint set -f "main.cpp" -l 138
output: Breakpoint 1: where = a.out`dotest() + 101 at main.cpp:138:5, address = 0x0000000100001b05


Expecting pattern: ^Breakpoint (?P<bpno>[0-9]+): (?P<num_locations>[0-9]+) locations\.$
Not matched

Expecting pattern: ^Breakpoint (?P<bpno>[0-9]+): (?P<num_locations>no) locations \(pending\)\.
Not matched

Expecting pattern: ^Breakpoint (?P<bpno>[0-9]+): where = (?P<module>.*)`(?P<symbol>[+\-]{0,1}[^+]+)( \+ (?P<offset>[0-9]+)){0,1}( \[inlined\] (?P<inline_symbol>.*)){0,1} at (?P<file>[^:]+):(?P<line_no>[0-9]+)(?P<column>(:[0-9]+)?), address = (?P<address>0x[0-9a-fA-F]+)$
Matched

runCmd: breakpoint set -f "main.cpp" -l 184
output: Breakpoint 2: where = a.out`main + 22 at main.cpp:184:5, address = 0x00000001000039b6


Expecting pattern: ^Breakpoint (?P<bpno>[0-9]+): (?P<num_locations>[0-9]+) locations\.$
Not matched

Expecting pattern: ^Breakpoint (?P<bpno>[0-9]+): (?P<num_locations>no) locations \(pending\)\.
Not matched

Expecting pattern: ^Breakpoint (?P<bpno>[0-9]+): where = (?P<module>.*)`(?P<symbol>[+\-]{0,1}[^+]+)( \+ (?P<offset>[0-9]+)){0,1}( \[inlined\] (?P<inline_symbol>.*)){0,1} at (?P<file>[^:]+):(?P<line_no>[0-9]+)(?P<column>(:[0-9]+)?), address = (?P<address>0x[0-9a-fA-F]+)$
Matched

runCmd: breakpoint set -f "main.cpp" -l 53
output: Breakpoint 3: where = a.out`breakpoint_func(void*) + 343 at main.cpp:53:17, address = 0x0000000100001147


Expecting pattern: ^Breakpoint (?P<bpno>[0-9]+): (?P<num_locations>[0-9]+) locations\.$
Not matched

Expecting pattern: ^Breakpoint (?P<bpno>[0-9]+): (?P<num_locations>no) locations \(pending\)\.
Not matched

Expecting pattern: ^Breakpoint (?P<bpno>[0-9]+): where = (?P<module>.*)`(?P<symbol>[+\-]{0,1}[^+]+)( \+ (?P<offset>[0-9]+)){0,1}( \[inlined\] (?P<inline_symbol>.*)){0,1} at (?P<file>[^:]+):(?P<line_no>[0-9]+)(?P<column>(:[0-9]+)?), address = (?P<address>0x[0-9a-fA-F]+)$
Matched

runCmd: breakpoint list -f
output: Current breakpoints:
1: file = 'main.cpp', line = 138, exact_match = 0, locations = 1
  1.1: where = a.out`dotest() + 101 at main.cpp:138:5, address = a.out[0x0000000100001b05], unresolved, hit count = 0 

2: file = 'main.cpp', line = 184, exact_match = 0, locations = 1
  2.1: where = a.out`main + 22 at main.cpp:184:5, address = a.out[0x00000001000039b6], unresolved, hit count = 0 

3: file = 'main.cpp', line = 53, exact_match = 0, locations = 1
  3.1: where = a.out`breakpoint_func(void*) + 343 at main.cpp:53:17, address = a.out[0x0000000100001147], unresolved, hit count = 0 



Expecting sub string: : file = 'main.cpp', line = 184
Matched

Expecting sub string: : file = 'main.cpp', line = 184
Matched

Expecting sub string: : file = 'main.cpp', line = 184
Matched

runCmd: run
runCmd failed!
error: process exited with status -1 (Error 1)


Command 'run' failed!

FAIL: LLDB (/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/clang_701_build/bin/clang-7-x86_64) :: test (TestConcurrentDelaySignalBreak.ConcurrentDelaySignalBreak)
<bound method SBProcess.Kill of <lldb.SBProcess; proxy of <Swig Object of type 'lldb::SBProcess *' at 0x107ba4f30> >>: success

Restore dir to: /Users/buildslave/jenkins/workspace/lldb-cmake-matrix/lldb-build/tools/lldb/lit
======================================================================
FAIL: test (TestConcurrentDelaySignalBreak.ConcurrentDelaySignalBreak)
   Test (1-second delay) signal and a breakpoint in multiple threads.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/packages/Python/lldbsuite/test/decorators.py", line 141, in wrapper
    func(*args, **kwargs)
  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/functionalities/thread/concurrent_events/TestConcurrentDelaySignalBreak.py", line 24, in test
    num_delay_signal_threads=1)
  File "/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/packages/Python/lldbsuite/test/concurrent_base.py", line 140, in do_thread_actions
    self.runCmd("run", RUN_SUCCEEDED)
  File "/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/llvm-project/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 2068, in runCmd
    msg if (msg) else CMD_MSG(cmd))
AssertionError: False is not True : Process is launched successfully
Error output:
error: process exited with status -1 (Error 1)

Config=x86_64-/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/clang_701_build/bin/clang-7
----------------------------------------------------------------------
Ran 1 test in 2.395s

RESULT: FAILED (0 passes, 1 failures, 0 errors, 0 skipped, 0 expected failures, 0 unexpected successes)