The cache configuration for test/csuite/timestamp_abort is a 20MB cache:

#define ENV_CONFIG_DEF                                        \
     "cache_size=20M,create,"                                  \
     "eviction_updates_trigger=95,eviction_updates_target=80," \

That means the test is allowing up to 4MB of dirty content in cache. The application allows for up to 200 threads - each of those threads is updating content and can pin content in the cache. The default leaf_page_max is 32k.

We should update the cache configuration of timestamp_abort to choose a more reasonable cache size. Perhaps scaling with the number of configured threads, and almost certainly increasing the eviction_dirty configurations. Using a slightly larger cache will allow the test to get more work done, and should uncover more bugs.