Stella Stamenova 7a8865cea8 [lldbsuite] Make the names of test classes unique ... Summary: If the names are not unique, the tests overwrite each other's results and logs. This also causes failures on platforms where the files are locked for writing. The names of the class/test pairs *have to* always be unique. The easiest way to achieve that is to name each class differently (usually the same as the file name). Reviewers: jasonmolenda, asmith Subscribers: clayborg, nemanjai, kbarton, lldb-commits Differential Revision: https://reviews.llvm.org/D53297 llvm-svn: 344547		2018-10-15 19:51:21 +00:00
..
a.yaml
gdbclientutils.py	Commit my attempt to test the change to ProcessGDBRemote	2018-09-12 21:35:02 +00:00
operating_system.py	Re-land "Don't assume backing thread shares protocol ID."	2018-04-13 11:31:34 +00:00
TestGDBRemoteClient.py	[lit] Fix several tests that fail when using Python 3 or on Windows	2018-05-14 21:04:24 +00:00
TestGDBRemoteLoad.py	Add a test for setting the load address of a module with differing physical/virtual addresses	2018-03-26 11:45:32 +00:00
TestRestartBug.py	Rewrite the flaky test_restart_bug test in a more deterministic way	2018-02-08 10:37:23 +00:00
TestStopPCs.py	[lldbsuite] Make the names of test classes unique	2018-10-15 19:51:21 +00:00
TestTargetXMLArch.py	Update TestTargetXMLArch.py test for llvm triple change with unspecified	2018-08-13 21:20:29 +00:00
TestThreadSelectionBug.py	Re-land "Don't assume backing thread shares protocol ID."	2018-04-13 11:31:34 +00:00