From 86e4d7ea35eee5329e960d20dedda02ff9968aad Mon Sep 17 00:00:00 2001 From: Stella Stamenova Date: Mon, 1 Jul 2019 22:12:55 +0000 Subject: [PATCH] [lldb] [lldbsuite] Use a unique class name for TestValueVarUpdate It looks like when this test was added, it was based on TestHelloWorld 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: 364860 --- .../lldbsuite/test/python_api/value_var_update/TestValueVarUpdate.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lldb/packages/Python/lldbsuite/test/python_api/value_var_update/TestValueVarUpdate.py b/lldb/packages/Python/lldbsuite/test/python_api/value_var_update/TestValueVarUpdate.py index a83fd6e..866d2a5 100644 --- a/lldb/packages/Python/lldbsuite/test/python_api/value_var_update/TestValueVarUpdate.py +++ b/lldb/packages/Python/lldbsuite/test/python_api/value_var_update/TestValueVarUpdate.py @@ -13,7 +13,7 @@ from lldbsuite.test.lldbtest import * from lldbsuite.test import lldbutil -class HelloWorldTestCase(TestBase): +class ValueVarUpdateTestCase(TestBase): mydir = TestBase.compute_mydir(__file__) -- 2.7.4