-
Notifications
You must be signed in to change notification settings - Fork 14.8k
[lldb] Fix failing test in TestClangREPL #154339
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
base: main
Are you sure you want to change the base?
Conversation
@llvm/pr-subscribers-lldb Author: Anutosh Bhat (anutosh491) ChangesAddressing #153560 The test runs as expected now
Full diff: https://github.com/llvm/llvm-project/pull/154339.diff 1 Files Affected:
diff --git a/lldb/test/API/repl/clang/TestClangREPL.py b/lldb/test/API/repl/clang/TestClangREPL.py
index 3152018865b1e..ffa598b650937 100644
--- a/lldb/test/API/repl/clang/TestClangREPL.py
+++ b/lldb/test/API/repl/clang/TestClangREPL.py
@@ -30,8 +30,9 @@ def start_repl(self):
self.expect("b main", substrs=["Breakpoint 1", "address ="])
self.expect("run", substrs=["stop reason = breakpoint 1"])
- # Start the REPL.
- self.child.send("expression --repl -l c --\n")
+ # Start the REPL with a harmless trailing input to trigger the warning.
+ self.child.send("expression --repl -l c -- 3 + 3\n")
+ self.child.expect_exact("Warning: trailing input is ignored in --repl mode")
self.child.expect_exact("1>")
# PExpect uses many timeouts internally and doesn't play well
@@ -56,16 +57,6 @@ def test_basic_completion(self):
self.quit()
- # Re-enter the REPL with trailing input to trigger warning.
- self.child.send("expression --repl -l c -- 3 + 3\n")
- self.child.expect_exact("Warning: trailing input is ignored in --repl mode\n")
- self.child.expect_exact("1>")
-
- # Evaluate another expression after warning.
- self.expect_repl("4 + 4", substrs=["(int) $3 = 8"])
-
- self.quit()
-
# PExpect uses many timeouts internally and doesn't play well
# under ASAN on a loaded machine..
@skipIfAsan
|
Hi @anutosh491 just referencing my comment #153560 (comment) Greendragon must always be green, to make sure we catch any issues that break the tests, I reverted the change in #153560 Please make sure you reland the change with your fix in this current patch (assuming it works) thanks! |
Thanks @rastogishubham . I've reapplied the patch ! |
Addressing #153560
The test runs as expected now