Details
-
Task
-
Resolution: Fixed
-
Major
-
6.5.0
Description
When running ep-engine_ep_unit_tests under ThreadSanitizer, the total test runtime is more than 10 minutes - for example:
00:19:20.852 Start 22: ep-engine_ep_unit_tests
|
00:30:53.164 31/177 Test #22: ep-engine_ep_unit_tests ...................................................... Passed 692.31 sec
|
Job: http://cv.jenkins.couchbase.com/job/kv_engine-threadsanitizer-master/10499/console
Compare this to a normal Linux build which takes less than 30 seconds - TSan is ~20x slower:
00:08:35.129 Start 25: ep-engine_ep_unit_tests
|
00:08:58.527 27/198 Test #25: ep-engine_ep_unit_tests ...................................................... Passed 23.38 sec
|
This isn't expected - TSan should generally be ~10x slower.
This is one of (if not the) slowest test when running under TSan - if we can improve it this should reduce the overall runtime of the TSan build.
Attachments
For Gerrit Dashboard: MB-33861 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
124455,13 | MB-33861: Split ep-engine_ep_engine_tests into multiple test suites | master | kv_engine | Status: MERGED | +2 | +1 |
124915,1 | MB-33861: Shorten GTest names to avoid Win32 MAX_PATH issues | master | kv_engine | Status: ABANDONED | 0 | -1 |