[swift-lldb-dev] Mysterious failure in lldbsuite.test.lldbtest.TestREPLThrowReturn

[Douglas Gregor]

Anyone know what’s going on here? There’s very little information in the log from

	https://ci.swift.org/job/swift-PR-Linux-smoke-test/565/consoleFull#-161933955fca400bf-2f4a-462e-b517-e058d770b2d7

it’s been failing consistently on Linux since this went in earlier today:

	https://github.com/apple/swift-lldb/commit/119fcb317c16ec30c20b63a1838da39302317352

making smoke testing mostly useless.

	- Doug

======================================================================
ERROR: test_with_dwarf (lldbsuite.test.lldbtest.TestREPLThrowReturn)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/lldb/packages/Python/lldbsuite/test/lldbinrepl.py", line 129, in __test_with_dwarf
    self.do_test()
  File "/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/lldb/packages/Python/lldbsuite/test/lldbinrepl.py", line 154, in do_test
    parser.handle_breakpoint(self, thread, breakpoint_id)
  File "/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/lldb/packages/Python/lldbsuite/test/lldbinrepl.py", line 65, in handle_breakpoint
    options.SetREPLMode(True)
  File "/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/buildbot_linux/lldb-linux-x86_64/lib/python2.7/site-packages/lldb/__init__.py", line 3987, in <lambda>
    __getattr__ = lambda self, name: _swig_getattr(self, SBExpressionOptions, name)
  File "/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/buildbot_linux/lldb-linux-x86_64/lib/python2.7/site-packages/lldb/__init__.py", line 79, in _swig_getattr
    raise AttributeError(name)
AttributeError: SetREPLMode
Config=x86_64-/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/buildbot_linux/llvm-linux-x86_64/bin/clang-3.9
----------------------------------------------------------------------
Ran 1 test in 2.985s

RESULT: FAILED (0 passes, 0 failures, 1 errors, 0 skipped, 0 expected failures, 0 unexpected successes)
Session logs for test failures/errors/unexpected successes can be found in directory '2016-08-04-23_42_49'