summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorStella Stamenova <stilis@microsoft.com>2019-07-01 18:13:20 +0000
committerStella Stamenova <stilis@microsoft.com>2019-07-01 18:13:20 +0000
commit55d2e6f1c26c5dc73815e67733db0e91c10f05c7 (patch)
treec6a30d546e4a55548fbcf5ccf30a32ab7e2e0465 /lldb/packages/Python/lldbsuite/test
parent9470bb262b545b849e5b9f4afa6e5a7fb28e5c75 (diff)
downloadbcm5719-llvm-55d2e6f1c26c5dc73815e67733db0e91c10f05c7.tar.gz
bcm5719-llvm-55d2e6f1c26c5dc73815e67733db0e91c10f05c7.zip
[lldb] [lldbsuite] Use a unique class name for TestBacktraceAll
It looks like when this test was added, it was based on TestBreakAfterJoin and it ended up with the same class name. This is an issue because the logs associated with the tests use the class name as the identifier for the file and if two tests have the same name their logs overwrite each other. On non-windows, this just means we lose one of the logs, but on Windows this means that one of the tests will fail occasionally because the file are locked by the other test. llvm-svn: 364826
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
-rw-r--r--lldb/packages/Python/lldbsuite/test/functionalities/thread/backtrace_all/TestBacktraceAll.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/thread/backtrace_all/TestBacktraceAll.py b/lldb/packages/Python/lldbsuite/test/functionalities/thread/backtrace_all/TestBacktraceAll.py
index e2026267c60..18928850ec8 100644
--- a/lldb/packages/Python/lldbsuite/test/functionalities/thread/backtrace_all/TestBacktraceAll.py
+++ b/lldb/packages/Python/lldbsuite/test/functionalities/thread/backtrace_all/TestBacktraceAll.py
@@ -11,7 +11,7 @@ from lldbsuite.test.lldbtest import *
from lldbsuite.test import lldbutil
-class BreakpointAfterJoinTestCase(TestBase):
+class BacktraceAllTestCase(TestBase):
mydir = TestBase.compute_mydir(__file__)
OpenPOWER on IntegriCloud