[LLDB] Fix sync issue in TestVSCode_launch.test_progress_events
This fixes flakiness in TestVSCode_launch.test_progress_events
vscode.progress_events some times failed to populate in time for
follow up iterations.
Adding a minor delay before the the for the loop fixes the issue.
Reviewed By: clayborg
Differential Revision: https://reviews.llvm.org/D99497
GitOrigin-RevId: b468f0e165ed67c5b1046b295b65e446afee62aa
diff --git a/test/API/tools/lldb-vscode/launch/TestVSCode_launch.py b/test/API/tools/lldb-vscode/launch/TestVSCode_launch.py
index aceed56..dc4549c 100644
--- a/test/API/tools/lldb-vscode/launch/TestVSCode_launch.py
+++ b/test/API/tools/lldb-vscode/launch/TestVSCode_launch.py
@@ -454,7 +454,6 @@
@skipIfWindows
@skipIfRemote
- @skipIf(oslist=["linux"])
def test_progress_events(self):
'''
Tests the progress events to ensure we are receiving them.
@@ -486,6 +485,8 @@
# Iterate over all progress events and save all start and end IDs, and
# remember any shared libraries that got symbol table parsing progress
# events.
+ # Sleep for 2 seconds to make sure progress_events gets populated
+ time.sleep(2)
for progress_event in self.vscode.progress_events:
event_type = progress_event['event']
if event_type == 'progressStart':