This test failed once for me on the (not-yet-connected-to-the-buildmaster) FreeBSD 11 builder as well:

======================================================================
FAIL: test_driver_batch_mode_dwo (TestBatchMode.DriverBatchModeTest)
Test that the lldb driver's batch mode works correctly.

Traceback (most recent call last):
File "/usr/home/user/llvm/tools/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 578, in wrapper
return func(self, *args, **kwargs)
File "/usr/home/user/llvm/tools/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 2306, in dwo_test_method
return attrvalue(self)
File "/usr/home/user/llvm/tools/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 862, in wrapper
func(*args, **kwargs)
File "/usr/home/user/llvm/tools/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 781, in wrapper
func(*args, **kwargs)
File "/usr/home/user/llvm/tools/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 636, in wrapper
func(*args, **kwargs)
File "/usr/home/user/llvm/tools/lldb/packages/Python/lldbsuite/test/driver/batch_mode/TestBatchMode.py", line 24, in test_driver_batch_mode
self.batch_mode()
File "/usr/home/user/llvm/tools/lldb/packages/Python/lldbsuite/test/driver/batch_mode/TestBatchMode.py", line 58, in batch_mode
self.expect_string ("continue")
File "/usr/home/user/llvm/tools/lldb/packages/Python/lldbsuite/test/driver/batch_mode/TestBatchMode.py", line 40, in expect_string
self.fail ("Timed out waiting for '%s'"%(string))
AssertionError: Timed out waiting for 'continue'
Config=x86_64-/usr/bin/cc

Annotation removed in http://llvm.org/viewvc/llvm-project?rev=257656&view=rev

Annotation removed in http://llvm.org/viewvc/llvm-project?rev=257656&view=rev

The annotation was removed from TestCommandScriptImmediateOutput, which is a new test an the annotation ended up there only due to copy-paste. TestBatchMode is still marked as flaky and it is flaky, see build e.g., 10321 http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/10321/steps/test2/logs/stdio.

After looking at this again, I suspect this might be actually a duplicate of bug llvm/llvm-bugzilla-archive#25652 (at least the linux issue).

*** Bug #23158 has been marked as a duplicate of this bug. ***