diff options
| author | Jonas Devlieghere <jonas@devlieghere.com> | 2025-09-04 16:37:41 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-04 16:37:41 -0700 |
| commit | 820f4402745dda82fca482f2b83925e2953e6ad9 (patch) | |
| tree | e4e8cc10b5ed14a8f91e0e0a85092e2600271a33 /lldb/test/API/python_api | |
| parent | fb5626fdd52905a0f4ade44221f83f0e469b9a8c (diff) | |
| download | llvm-820f4402745dda82fca482f2b83925e2953e6ad9.zip llvm-820f4402745dda82fca482f2b83925e2953e6ad9.tar.gz llvm-820f4402745dda82fca482f2b83925e2953e6ad9.tar.bz2 | |
[lldb] Correct style of error messages (#156774)
The LLVM Style Guide says the following about error and warning messages
[1]:
> [T]o match error message styles commonly produced by other tools,
> start the first sentence with a lowercase letter, and finish the last
> sentence without a period, if it would end in one otherwise.
I often provide this feedback during code review, but we still have a
bunch of places where we have inconsistent error message, which bothers
me as a user. This PR identifies a handful of those places and updates
the messages to be consistent.
[1] https://llvm.org/docs/CodingStandards.html#error-and-warning-messages
Diffstat (limited to 'lldb/test/API/python_api')
| -rw-r--r-- | lldb/test/API/python_api/interpreter/TestRunCommandInterpreterAPI.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lldb/test/API/python_api/interpreter/TestRunCommandInterpreterAPI.py b/lldb/test/API/python_api/interpreter/TestRunCommandInterpreterAPI.py index f677b86..4565987 100644 --- a/lldb/test/API/python_api/interpreter/TestRunCommandInterpreterAPI.py +++ b/lldb/test/API/python_api/interpreter/TestRunCommandInterpreterAPI.py @@ -105,7 +105,7 @@ class CommandRunInterpreterAPICase(TestBase): self.assertFalse(has_crashed) self.assertIn("invalid target", result_str) - self.assertIn("No auto repeat", result_str) + self.assertIn("no auto repeat", result_str) class SBCommandInterpreterRunOptionsCase(TestBase): |