[Lldb-commits] [lldb] [lldb] New expedited register specfication for unavailable regs (PR #193894)
Jason Molenda via lldb-commits
lldb-commits at lists.llvm.org
Mon May 11 00:49:57 PDT 2026
jasonmolenda wrote:
The build & test linux fail r.n. on the PR test bot is
```
2026-05-11T07:45:28.0081969Z ======================================================================
2026-05-11T07:45:28.0082538Z FAIL: test_run_locker (TestRunLocker.TestRunLocker.test_run_locker)
2026-05-11T07:45:28.0083147Z Test that the run locker is set correctly when we launch
2026-05-11T07:45:28.0083830Z ----------------------------------------------------------------------
2026-05-11T07:45:28.0084420Z Traceback (most recent call last):
2026-05-11T07:45:28.0085389Z File "/home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/packages/Python/lldbsuite/test/decorators.py", line 160, in wrapper
2026-05-11T07:45:28.0086298Z return func(*args, **kwargs)
2026-05-11T07:45:28.0086667Z ^^^^^^^^^^^^^^^^^^^^^
2026-05-11T07:45:28.0088022Z File "/home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/python_api/run_locker/TestRunLocker.py", line 23, in test_run_locker
2026-05-11T07:45:28.0089011Z self.runlocker_test(False)
2026-05-11T07:45:28.0089855Z File "/home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/python_api/run_locker/TestRunLocker.py", line 110, in runlocker_test
2026-05-11T07:45:28.0090803Z self.assertIn(
2026-05-11T07:45:28.0091334Z AssertionError: "can't evaluate expressions when the process is running" not found in ''
```
idk what that is, I'm guessing it's spurious and will go away on re-rest, I might do a whitespace commit to trigger a re-run.
https://github.com/llvm/llvm-project/pull/193894
More information about the lldb-commits
mailing list