-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[lldb] Put the new debugger in synchronous mode in TestGlobalModuleCache #98041
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
In async mode, the test terminates sooner that it should (`run_to_source_breakpoint` does not work in this mode), and then the test crashes due to llvm#98038. Most of the time, the test does not fail because its already XFAILed, but the crash still registers as a failure.
@llvm/pr-subscribers-lldb Author: Pavel Labath (labath) ChangesIn async mode, the test terminates sooner that it should ( Full diff: https://github.com/llvm/llvm-project/pull/98041.diff 1 Files Affected:
diff --git a/lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py b/lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py
index 0942dcd655b75..ccefc28946e06 100644
--- a/lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py
+++ b/lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py
@@ -111,6 +111,7 @@ def do_test(self, one_target, one_debugger):
else:
if one_target:
new_debugger = lldb.SBDebugger().Create()
+ new_debugger.SetAsync(False)
self.old_debugger = self.dbg
self.dbg = new_debugger
|
This explains why the |
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/59/builds/1234 Here is the relevant piece of the build log for the reference:
|
…che (llvm#98041) In async mode, the test terminates sooner than it should (`run_to_source_breakpoint` does not work in this mode), and then the test crashes due to llvm#76057. Most of the time, the test does not fail because its already XFAILed, but the crash still registers as a failure.
In async mode, the test terminates sooner than it should (
run_to_source_breakpoint
does not work in this mode), and then the test crashes due to #76057. Most of the time, the test does not fail because its already XFAILed, but the crash still registers as a failure.