Skip to content

Commit dbcf4a7

Browse files
JDevlieghereadrian-prantl
authored andcommitted
[lldb] Re-enable TestVSCode_launch on Darwin
The test was disabled because it was supposedly flakey. I'm not able to reproduce any flakiness. I ran the test in a look with different levels of parallelization and load. Re-enabling the test and monitoring the Darwin bots. (cherry picked from commit 6bdf485)
1 parent 26389c3 commit dbcf4a7

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

lldb/test/API/tools/lldb-vscode/launch/TestVSCode_launch.py

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,6 @@
1414

1515
class TestVSCode_launch(lldbvscode_testcase.VSCodeTestCaseBase):
1616
@skipIfWindows
17-
@skipIfDarwin # Flaky
1817
@skipIfRemote
1918
def test_default(self):
2019
"""
@@ -423,10 +422,10 @@ def test_extra_launch_commands(self):
423422

424423
@skipIfWindows
425424
@skipIfNetBSD # Hangs on NetBSD as well
426-
@skipIfDarwin
427425
@skipIf(
428-
archs=["arm", "aarch64"]
429-
) # Example of a flaky run http://lab.llvm.org:8011/builders/lldb-aarch64-ubuntu/builds/5540/steps/test/logs/stdio
426+
archs=["arm", "aarch64"],
427+
oslist=["linux"]
428+
)
430429
def test_terminate_commands(self):
431430
"""
432431
Tests that the "terminateCommands", that can be passed during

0 commit comments

Comments
 (0)