[Lldb-commits] [lldb] [lldb] rename fooSynthProvider module (PR #118094)

[via lldb-commits]

dlav-sc wrote:

> Seems fine but please expand on `Currently SyntheticCappingTestCase fails with` to say where it fails. 

I can provide the fail log. Looks like lldb firstly runs `PythonSynthDataFormatterTestCase` and then `SyntheticCappingTestCase`, but it doesn't really matter, because if lldb run the tests in another order, `PythonSynthDataFormatterTestCase` would fail with the same problem instead of `SyntheticCappingTestCase` I suppose. Also I've tried to run `SyntheticCappingTestCase` alone using a filter option of the `dotest.py` script and the test passes in that case.

```
======================================================================
FAIL: test_with_run_command_dwarf (TestSyntheticCapping.SyntheticCappingTestCase.test_with_run_command_dwarf)
      Check for an issue where capping does not work because the Target pointer appears to be changing behind our backs.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/daniil/llvm-project/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 1760, in test_method
    return attrvalue(self)
           ^^^^^^^^^^^^^^^
  File "/home/daniil/llvm-project/lldb/test/API/functionalities/data-formatter/synthcapping/TestSyntheticCapping.py", line 73, in test_with_run_command
    self.expect(
  File "/home/daniil/llvm-project/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 2466, in expect
    self.fail(log_msg)
AssertionError: Ran command:
"script fooSynthProvider.fooSynthProvider.reset_max_num_children_max()"
Got output:
Traceback (most recent call last):
  File "<input>", line 1, in <module>
AttributeError: type object 'fooSynthProvider' has no attribute 'reset_max_num_children_max'
Expecting sub string: "257" (was not found)
======================================================================
FAIL: test_with_run_command_dwo (TestSyntheticCapping.SyntheticCappingTestCase.test_with_run_command_dwo)
      Check for an issue where capping does not work because the Target pointer appears to be changing behind our backs.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/daniil/llvm-project/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 1760, in test_method
    return attrvalue(self)
           ^^^^^^^^^^^^^^^
  File "/home/daniil/llvm-project/lldb/test/API/functionalities/data-formatter/synthcapping/TestSyntheticCapping.py", line 73, in test_with_run_command
    self.expect(
  File "/home/daniil/llvm-project/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 2466, in expect
    self.fail(log_msg)
AssertionError: Ran command:
"script fooSynthProvider.fooSynthProvider.reset_max_num_children_max()"
Got output:
Traceback (most recent call last):
  File "<input>", line 1, in <module>
AttributeError: type object 'fooSynthProvider' has no attribute 'reset_max_num_children_max'
Expecting sub string: "257" (was not found)
```

> I assume you are using a different kind of setup

Maybe it's true, I've tried to test lldb on riscv using dotest.py with remote debugging options.

https://github.com/llvm/llvm-project/pull/118094