From 35f26f613a37a4e7894a92440d4f2f20539d9b79 Mon Sep 17 00:00:00 2001 From: Pavel Labath Date: Tue, 16 Feb 2016 09:58:47 +0000 Subject: Mark TestLldbGdbServer.test_written_M_content_reads_back_correctly as flaky on linux I believe the root cause is the asynchronous arrival of inferior stdio (pr25652). llvm-svn: 260950 --- .../Python/lldbsuite/test/tools/lldb-server/TestLldbGdbServer.py | 1 + 1 file changed, 1 insertion(+) (limited to 'lldb/packages/Python/lldbsuite/test/tools') diff --git a/lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestLldbGdbServer.py b/lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestLldbGdbServer.py index 961aa5d9429..0c5c64e4072 100644 --- a/lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestLldbGdbServer.py +++ b/lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestLldbGdbServer.py @@ -1318,6 +1318,7 @@ class LldbGdbServerTestCase(gdbremote_testcase.GdbRemoteTestCaseBase): self.written_M_content_reads_back_correctly() @llgs_test + @expectedFlakeyLinux("llvm.org/pr25652") def test_written_M_content_reads_back_correctly_llgs(self): self.init_llgs_test() self.build() -- cgit v1.2.3