[lldb] Remote accidental logs left in TestGuiExpandThreadsTree
[lldb] Disable TestGuiExpandThreadsTree
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://r
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://reviews.llvm.org/D128077
show more ...
[lldb][gui] use just '#2' instead of 'frame #2' in the threads/frame viewSince the threads/frame view is taking only a small part on the right sideof the screen, only a part of the function name o
[lldb][gui] use just '#2' instead of 'frame #2' in the threads/frame viewSince the threads/frame view is taking only a small part on the right sideof the screen, only a part of the function name of each frame is visible.It seems rather wasteful to spell out 'frame' there when it's obviousthat it is a frame, it's better to use the space for more of the functionname.Differential Revision: https://reviews.llvm.org/D122998
[lldb] Speculative fix to TestGuiExpandThreadsTreeThis test relies on being able to unwind from an arbitrary place insidelibc. While I am not sure this is the cause of the observed flakyness,it i
[lldb] Speculative fix to TestGuiExpandThreadsTreeThis test relies on being able to unwind from an arbitrary place insidelibc. While I am not sure this is the cause of the observed flakyness,it is known that we are not able to unwind correctly from some places in(linux) libc.This patch adds additional synchronization to ensure that the inferioris in the main function (instead of pthread guts) when lldb tries tounwind it. At the very least, it should make the test runs morepredictable/repeatable.
[LLDB] Skip flaky tests on Arm/AArch64 Linux botsFollowing LLDB tests fail randomly on LLDB Arm/AArch64 Linux buildbots.We still not have a reliable solution for these tests to passconsistently.
[LLDB] Skip flaky tests on Arm/AArch64 Linux botsFollowing LLDB tests fail randomly on LLDB Arm/AArch64 Linux buildbots.We still not have a reliable solution for these tests to passconsistently. I am marking them skipped for now.TestBreakpointCallbackCommandSource.pyTestIOHandlerResize.pyTestEditline.pyTestGuiViewLarge.pyTestGuiExpandThreadsTree.pyTestGuiBreakpoints.py
Revert "Revert "[LLDB][GUI] Expand selected thread tree item by default""This reverts commit fd18f0e84cca023df6cb19e88c07c0e2059f659b.I reverted this change to see its effect on failing GUI tests
Revert "Revert "[LLDB][GUI] Expand selected thread tree item by default""This reverts commit fd18f0e84cca023df6cb19e88c07c0e2059f659b.I reverted this change to see its effect on failing GUI tests on LLDBArm/AArch64 Linux buildbots. I could not find any evidence against thisparticular change so reverting it back.Differential Revision: https://reviews.llvm.org/D100243
Revert "[LLDB][GUI] Expand selected thread tree item by default"This reverts commit fed25ddc1c3de59aa1de27e95b349f86896ccb79.There has been sporadic failures in LLDB AArch64/Arm 32 buildbots sinc
Revert "[LLDB][GUI] Expand selected thread tree item by default"This reverts commit fed25ddc1c3de59aa1de27e95b349f86896ccb79.There has been sporadic failures in LLDB AArch64/Arm 32 buildbots sincethis commit. I am temporarily reverting it see if it fixes the issue.Differential Revision: https://reviews.llvm.org/D100243
[LLDB][GUI] Expand selected thread tree item by defaultThis patch expands the tree item that corresponds to the selected threadby default in the Threads window. Additionally, the tree root item is
[LLDB][GUI] Expand selected thread tree item by defaultThis patch expands the tree item that corresponds to the selected threadby default in the Threads window. Additionally, the tree root item isalways expanded, which is the process in the Threads window.Reviewed By: clayborgDifferential Revision: https://reviews.llvm.org/D100243