99451b4453
Summary: Moves lldbsuite tests to lldb/test/API.
This is a largely mechanical change, moved with the following steps:
```
rm lldb/test/API/testcases
mkdir -p lldb/test/API/{test_runner/test,tools/lldb-{server,vscode}}
mv lldb/packages/Python/lldbsuite/test/test_runner/test lldb/test/API/test_runner
for d in $(find lldb/packages/Python/lldbsuite/test/* -maxdepth 0 -type d | egrep -v "make|plugins|test_runner|tools"); do mv $d lldb/test/API; done
for d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-vscode -maxdepth 1 -mindepth 1 | grep -v ".py"); do mv $d lldb/test/API/tools/lldb-vscode; done
for d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-server -maxdepth 1 -mindepth 1 | egrep -v "gdbremote_testcase.py|lldbgdbserverutils.py|socket_packet_pump.py"); do mv $d lldb/test/API/tools/lldb-server; done
```
lldb/packages/Python/lldbsuite/__init__.py and lldb/test/API/lit.cfg.py were also updated with the new directory structure.
Reviewers: labath, JDevlieghere
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D71151
23 lines
819 B
Plaintext
23 lines
819 B
Plaintext
"""Tests that a flakey fail is rerun, and will pass on the rerun.
|
|
Run this test with --rerun-all-issues specified to test that
|
|
the tests fail on the first run, then pass on the second.
|
|
Do not mark them as flakey as, at this time, flakey tests will
|
|
run twice, thus causing the second run to succeed."""
|
|
|
|
|
|
import rerun_base
|
|
|
|
import lldbsuite.test.lldbtest as lldbtest
|
|
|
|
|
|
class RerunFailTestCase(rerun_base.RerunBaseTestCase):
|
|
"""Forces test failure on first run, success on rerun."""
|
|
@lldbtest.no_debug_info_test
|
|
def test_buildbot_catches_failure(self):
|
|
"""Issues a failing test assertion."""
|
|
if self.should_generate_issue():
|
|
self.assertTrue(
|
|
False,
|
|
"This will fail on the first call, succeed on rerun, and "
|
|
"alternate thereafter.")
|