Author: Dmitry Vasilyev Date: 2024-05-14T20:05:22+04:00 New Revision: 0f17d9a28c40eebd42c83956e2a7b5186c1814d7
URL: https://github.com/llvm/llvm-project/commit/0f17d9a28c40eebd42c83956e2a7b5186c1814d7 DIFF: https://github.com/llvm/llvm-project/commit/0f17d9a28c40eebd42c83956e2a7b5186c1814d7.diff LOG: [lldb] Fixed the test TestThreadStates when run with a remote target (#92086) 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. Added: Modified: lldb/test/API/functionalities/thread/state/TestThreadStates.py Removed: ################################################################################ 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): _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
