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

2024-12-02 Thread Pavel Labath via lldb-commits
labath wrote: I don't run remote tests these days, but it sounds like you need to invoke the tests through lit rather than running tests directly. Here's some description of this: https://github.com/llvm/llvm-project/blob/4930f69b78e215c60eb53e25596599c2f98b6564/lldb/test/API/lit.cfg.py#L292

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

2024-12-02 Thread via lldb-commits
dlav-sc wrote: > I'd switch to the (standard) one-process-per-test mode. It's good you've written about this mode, because I haven't even known that lldb testsuite has such option. Could you provide more information how can I enable it, please? Is there a corresponding flag for a `dotest.py`?

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

2024-12-02 Thread Pavel Labath via lldb-commits
labath wrote: > Maybe it's true, I've tried to test lldb on riscv using dotest.py with remote > debugging options. It sounds like you're using the mode which runs all tests (files) in the same process. I don't know if anyone uses it these days (and this error sort of says "no"). I don't think

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

2024-11-29 Thread 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-commits] [lldb] [lldb] rename fooSynthProvider module (PR #118094)

2024-11-29 Thread David Spickett via lldb-commits
DavidSpickett wrote: Seems fine but please expand on `Currently SyntheticCappingTestCase fails with` to say where it fails. Linaro's bots don't have a problem with this test, so I assume you are using a different kind of setup. https://github.com/llvm/llvm-project/pull/118094 _

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

2024-11-29 Thread via lldb-commits
github-actions[bot] wrote: :warning: Python code formatter, darker found issues in your code. :warning: You can test this locally with the following command: ``bash darker --check --diff -r fedb9fdb98314ff0ddff065dbd6ef8b2b7e6ec96...11d1f52ea2bc578c9bd15646d653f5e2a1626750 lldb

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

2024-11-29 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: None (dlav-sc) Changes Currently SyntheticCappingTestCase fails with ``` AttributeError: type object 'fooSynthProvider' has no attribute 'reset_max_num_children_max' ``` The source of the issue is that lldb during PythonSynthDataFormatterTe

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

2024-11-29 Thread via lldb-commits
https://github.com/dlav-sc created https://github.com/llvm/llvm-project/pull/118094 Currently SyntheticCappingTestCase fails with ``` AttributeError: type object 'fooSynthProvider' has no attribute 'reset_max_num_children_max' ``` The source of the issue is that lldb during PythonSynthDataForma