- User Since
- Jan 19 2019, 8:24 PM (180 w, 3 d)
Address @JDevlieghere comment
Wed, Jun 29
Not sure if this is related to this patch but TestGdbRemote_vContThreads.py is still timing out on the macOS bot:
Refactor logging code
Log only when verbose mode is enabled
Tue, Jun 28
There are some random test failures following this patch on lldb-debian-x86_64: https://lab.llvm.org/buildbot/#/builders/68/builds/34883
Mon, Jun 27
Use field identifiers instead of indices and add long-mode support.
This patch is causing a test to fail on the macOS bot:
Fri, Jun 24
Thu, Jun 23
This looks way better :) !
@cassanova You probably also want to implement this for the command-interpreter-fuzzer target
Wed, Jun 22
Tue, Jun 21
Hi @mgorny ! TestNonStop.py is also failing on the macOS bots: https://green.lab.llvm.org/green/job/lldb-cmake/44743/
Fri, Jun 17
Thu, Jun 16
Wed, Jun 15
A bit late to this ... thanks for your fix!
How is this any different from running ninja lldb-target-fuzzer ? I might be missing something ...
Fri, Jun 10
Thanks @kastiglione !
Thanks for clarifying! LGTM with a test!
Thu, Jun 9
What happens if you try to call str after your change ? I have no objection with this change, I think rather it will greatly improve manipulating SBTypes in the interpreter ! Just making sure this passes the test suite and doesn't break the previous behavior
Wed, Jun 8
Pretty cool but it would be nice to have the following formatting: "AssertionError: stopped (5) != exited (10) : message" ... I feel like it's easier to read this way
Tue, Jun 7
Even better! LGTM!
Makes more sense. LGTM!
Jun 3 2022
Thanks for writing that! I'm sure many users will find it very useful.
LGTM with some minor feedbacks :) !
May 23 2022
May 20 2022
May 19 2022
May 18 2022
Only run test on Darwin platforms
Address @JDevlieghere comments
May 16 2022
May 13 2022
Actually, landed this yesterday in a6926d576131c9ad849fef6f1d43134caab5025e