From fdfcd719a2b64d6c43c4d993b6efd5928dbe9648 Mon Sep 17 00:00:00 2001 From: Stella Stamenova Date: Tue, 27 Nov 2018 22:18:02 +0000 Subject: [lldbsuite] Each lldb suite test must have a unique class name A couple of new tests have been added that use existing class names. This causes failures on Windows if the tests run at the same time and on any platform it results in the logs being overwritten. llvm-svn: 347717 --- .../test/expression_command/radar_43822994/TestScopedEnumType.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lldb/packages/Python/lldbsuite/test/expression_command') diff --git a/lldb/packages/Python/lldbsuite/test/expression_command/radar_43822994/TestScopedEnumType.py b/lldb/packages/Python/lldbsuite/test/expression_command/radar_43822994/TestScopedEnumType.py index c900ba7979b..028047fc46b 100644 --- a/lldb/packages/Python/lldbsuite/test/expression_command/radar_43822994/TestScopedEnumType.py +++ b/lldb/packages/Python/lldbsuite/test/expression_command/radar_43822994/TestScopedEnumType.py @@ -7,7 +7,7 @@ from lldbsuite.test.lldbtest import * from lldbsuite.test import lldbutil -class ExprXValuePrintingTestCase(TestBase): +class ScopedEnumType(TestBase): mydir = TestBase.compute_mydir(__file__) -- cgit v1.2.3