[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 ...
Speculatively fix build botsThis should address build failures found in:https://lab.llvm.org/buildbot/#/builders/217/builds/3610https://lab.llvm.org/buildbot/#/builders/215/builds/4609https://l
Speculatively fix build botsThis should address build failures found in:https://lab.llvm.org/buildbot/#/builders/217/builds/3610https://lab.llvm.org/buildbot/#/builders/215/builds/4609https://lab.llvm.org/buildbot/#/builders/68/builds/31012
[lldb] Replace asserts on .Success() with assertSuccess()Replace forms of `assertTrue(err.Success())` with `assertSuccess(err)` (added in D82759).* `assertSuccess` prints out the error's message
[lldb] Replace asserts on .Success() with assertSuccess()Replace forms of `assertTrue(err.Success())` with `assertSuccess(err)` (added in D82759).* `assertSuccess` prints out the error's message* `assertSuccess` expresses explicit higher level semantics, both to the reader and for test failure output* `assertSuccess` seems not to be well known, using it where possible will help spread knowledge* `assertSuccess` statements are more succinctDifferential Revision: https://reviews.llvm.org/D119616
[lldb] Remove support for replaying the test suite from a reproducerThis patch removes the infrastructure to replay the test suite from areproducer, as well as the modifications made to the indivi
[lldb] Remove support for replaying the test suite from a reproducerThis patch removes the infrastructure to replay the test suite from areproducer, as well as the modifications made to the individual tests.
[LLDB] Skip TestExitDuringExpression on aarch64/linux buildbotTestExitDuringExpression test_exit_before_one_thread_no_unwind failssporadically on both Arm and AArch64 linux buildbots. This seems l
[LLDB] Skip TestExitDuringExpression on aarch64/linux buildbotTestExitDuringExpression test_exit_before_one_thread_no_unwind failssporadically on both Arm and AArch64 linux buildbots. This seems likemanifesting itself on a fully loaded machine. I have not found a reliabletimeout value so marking it skip for now.
[LLDB] Skip TestExitDuringExpression on aarch64/linux buildbotTestExitDuringExpression test_exit_before_one_thread_unwind failssporadically on both Arm and AArch64 linux buildbots.This seems like
[LLDB] Skip TestExitDuringExpression on aarch64/linux buildbotTestExitDuringExpression test_exit_before_one_thread_unwind failssporadically on both Arm and AArch64 linux buildbots.This seems like a thread timing issue. I am marking it skip for now.
[LLDB] Skip TestExitDuringExpression on arm/linux buildbotTestExitDuringExpression test_exit_before_one_thread_unwind failssporadically on arm/linux. This seems like a thread timing issue.I am ma
[LLDB] Skip TestExitDuringExpression on arm/linux buildbotTestExitDuringExpression test_exit_before_one_thread_unwind failssporadically on arm/linux. This seems like a thread timing issue.I am marking it skip for now.
[lldb] [test] Update test status for NetBSD
[lldb] [test] Link FreeBSD test failures to bugsDifferential Revision: https://reviews.llvm.org/D92740
[lldb] [test] Update XFAILs/skips for FreeBSDUpdate expected failures and test skips based on common resultsfor the old and new FreeBSD plugins.
[lldb/Reproducers] Skip or fix the remaining tests.After this patch all remaining tests should pass on macOS when replayedfrom a reproducer.To capture the reproducers: ./bin/llvm-lit ../llvm-
[lldb/Reproducers] Skip or fix the remaining tests.After this patch all remaining tests should pass on macOS when replayedfrom a reproducer.To capture the reproducers: ./bin/llvm-lit ../llvm-project/lldb/test/ --param lldb-run-with-repro=captureTo replay the reproducers: ./bin/llvm-lit ../llvm-project/lldb/test/ --param lldb-run-with-repro=replay
[lldb] Increase timeout in TestExitDuringExpression200 microseconds is not enough time for any expression to executereliably. On linux, calling pthread_exit can result in call to dlopen,which can
[lldb] Increase timeout in TestExitDuringExpression200 microseconds is not enough time for any expression to executereliably. On linux, calling pthread_exit can result in call to dlopen,which cannot complete in that time, particularly when running under adebugger.On linux, this test failed all the time, on macos, about two thirds ofruns were failing. This patch increases the timeout to 100ms, which isenough to get it passing reliably on linux, though I wouldn't besurprised if an even bigger timeout would be needed for remote testruns.
Maybe I need ENABLE_THREADS in the Makefile.
This very simple .c file is failing on the Debian bot wit the errorundefined reference to pthread_createI skipped the test till I can figure out why this didn't build.
Handle the case where a thread exits while we are running a function on it.