[Swift CI] [LLDB] [swift-3.0-preview-3] LLDB test failing on Ubuntu 15.10

Hi,

Can someone look at this test failure? It started after following commit.

https://ci.swift.org/view/swift-3.0-preview-3/job/oss-lldb-swift-3.0-preview-3-incremental-linux-ubuntu-15_10/23/console

[PCH/preamble] Make sure that if the preamble/PCH was serialized with (detail <https://ci.swift.org/view/swift-3.0-preview-3/job/oss-lldb-swift-3.0-preview-3-incremental-linux-ubuntu-15_10/22/changes#detail&gt;\)
[test] Add &#039;env&#039; to fix test failures in windows bots. (detail <https://ci.swift.org/view/swift-3.0-preview-3/job/oss-lldb-swift-3.0-preview-3-incremental-linux-ubuntu-15_10/22/changes#detail&gt;\)

···

======================================================================
FAIL: test_attach_to_process_by_name_gmodules (TestProcessAttach.ProcessAttachTestCase)
   Test attach by process name
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/buildnode/jenkins/workspace/oss-lldb-swift-3.0-preview-3-incremental-linux-ubuntu-15_10/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 1503, in gmodules_test_method
    return attrvalue(self)
  File "/home/buildnode/jenkins/workspace/oss-lldb-swift-3.0-preview-3-incremental-linux-ubuntu-15_10/lldb/packages/Python/lldbsuite/test/functionalities/process_attach/TestProcessAttach.py", line 47, in test_attach_to_process_by_name
    self.runCmd("process attach -n " + exe_name)
  File "/home/buildnode/jenkins/workspace/oss-lldb-swift-3.0-preview-3-incremental-linux-ubuntu-15_10/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 1812, in runCmd
    msg if msg else CMD_MSG(cmd))
AssertionError: False is not True : Command 'process attach -n ProcessAttach' returns successfully
Config=x86_64-/home/buildnode/jenkins/workspace/oss-lldb-swift-3.0-preview-3-incremental-linux-ubuntu-15_10/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang-3.9
----------------------------------------------------------------------
Ran 6 tests in 115.176s

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

===================
Test Result Summary

Test Methods: 2808
Reruns: 16
Success: 1780
Expected Failure: 169
Failure: 0
Error: 1
Exceptional Exit: 0
Unexpected Success: 42
Skip: 816
Timeout: 0
Expected Timeout: 0

Thanks,
Mishal Shah