Skip to content

Commit f9ad112

Browse files
committed
[lldb] Speed up TestValueObjectRecursion by making it a no_debug_info_test
This is one of the most expensive tests and runs for nearly half a minute on my machine. Beside this test just doing a lot of work by iterating 15k times on one ValueObject (which seems to be the point), it also runs this for every debug info variant which doesn't seem relevant to just iterating ValueObject. This marks it as no_debug_info_test to only run one debug info variation and cut down the runtime to around 7 seconds on my machine.
1 parent 0c2a4d3 commit f9ad112

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

lldb/test/API/functionalities/recursion/TestValueObjectRecursion.py

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@
66

77

88
import lldb
9+
from lldbsuite.test.decorators import *
910
from lldbsuite.test.lldbtest import *
1011
import lldbsuite.test.lldbutil as lldbutil
1112

@@ -20,6 +21,7 @@ def setUp(self):
2021
# Find the line number to break at.
2122
self.line = line_number('main.cpp', '// Set break point at this line.')
2223

24+
@no_debug_info_test
2325
def test_with_run_command(self):
2426
"""Test that deeply nested ValueObjects still work."""
2527
self.build()

0 commit comments

Comments
 (0)