llvmbot wrote:
<!--LLVM PR SUMMARY COMMENT-->
@llvm/pr-subscribers-lldb
Author: Dmitry Vasilyev (slydiman)
<details>
<summary>Changes</summary>
self.wait_for_running_event(process) is always called after
self.runCmd("continue"). It is strange to expect eStateConnected here. This
test failed in case of a remote target. The correct state is eStateRunning.
Removed incorrect checking.
---
Full diff: https://github.com/llvm/llvm-project/pull/92086.diff
1 Files Affected:
- (modified) lldb/test/API/functionalities/thread/state/TestThreadStates.py
(-4)
``````````diff
diff --git a/lldb/test/API/functionalities/thread/state/TestThreadStates.py
b/lldb/test/API/functionalities/thread/state/TestThreadStates.py
index f4c17df523382..4dbe230c0ce85 100644
--- a/lldb/test/API/functionalities/thread/state/TestThreadStates.py
+++ b/lldb/test/API/functionalities/thread/state/TestThreadStates.py
@@ -102,10 +102,6 @@ def thread_state_after_breakpoint_test(self):
def wait_for_running_event(self, process):
listener = self.dbg.GetListener()
- if lldb.remote_platform:
- lldbutil.expect_state_changes(
- self, listener, process, [lldb.eStateConnected]
- )
lldbutil.expect_state_changes(self, listener, process,
[lldb.eStateRunning])
def thread_state_after_continue_test(self):
``````````
</details>
https://github.com/llvm/llvm-project/pull/92086
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
