The test_timestamp_abort child process failed with:
The command that failed is test_timestamp_abort -m -h WT_TEST.timestamp-abort -T 16 -t 37.
There are a few things to note about this failure:
- This evergreen job has not run to completion for several weeks. So this is not necessarily a newly introduced problem.
- The table with the problem is the oplog-like table meaning it is logged and is using timestamps.
- The value on the page is 0xab which is WT_DEBUG_BYTE. This is set when wt_overwrite_and_free is called in several places when freeing blocks and pages, etc.