diff options
author | Pavel Labath <pavel@labath.sk> | 2019-04-21 13:02:41 +0000 |
---|---|---|
committer | Pavel Labath <pavel@labath.sk> | 2019-04-21 13:02:41 +0000 |
commit | e8687e6ee1ba16bb4b6b1d96bb30b155ae5df522 (patch) | |
tree | 7d05fcdbcc157a3782709adcba47744bfe860cc5 /lldb/packages/Python/lldbsuite/test/tools/lldb-mi/signal/TestMiSignal.py | |
parent | 27e9d982eb1e5aaa4c06a8771a3430eb803c1edf (diff) | |
download | bcm5719-llvm-e8687e6ee1ba16bb4b6b1d96bb30b155ae5df522.tar.gz bcm5719-llvm-e8687e6ee1ba16bb4b6b1d96bb30b155ae5df522.zip |
Make TestVSCode_step pass reliably
Summary:
The test was failing occasionally (1% of runs or so), because of
unpredictable timings between the two threads spawned by the test. If
the second thread hit the breakpoint right as we were stepping out of
the function on the first thread, we would still be stuck at the inner
frame when the process stopped.
This would cause errors like:
File "/home/worker/lldb-x86_64-debian/lldb-x86_64-debian/llvm/tools/lldb/packages/Python/lldbsuite/test/tools/lldb-vscode/step/TestVSCode_step.py", line 67, in test_step
self.assertEqual(x1, x3, 'verify step out variable')
AssertionError: 2 != 1 : verify step out variable
AFAICT, lldb-vscode is doing the right thing here, and the problem is
that the test is not taking this sequence of events into account. Since
the test is about testing stepping, it does not seem necessary to have
threads in the inferior at all, so I just rewrite the test to execute
the code we're supposed to step through directly on the main thread.
Reviewers: clayborg, jgorbe
Subscribers: jfb, lldb-commits
Differential Revision: https://reviews.llvm.org/D60608
llvm-svn: 358847
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/tools/lldb-mi/signal/TestMiSignal.py')
0 files changed, 0 insertions, 0 deletions