Some runs of test format have started producing the following assertion error whilst it opens a backed up database in recovery:
[2021/06/03 12:25:00.851] t: huffman_key=0: WARNING, ignoring unknown configuration keyword [2021/06/03 12:25:00.851] t: transaction.isolation=snapshot: WARNING, ignoring unknown configuration keyword [2021/06/03 12:25:11.037] [1622723111:37483][12363:0x7f7177fef700], file:wt.wt, txn-recover: __txn_commit_timestamps_assert, 1269: commit_timestamp required and none set on this transaction: Invalid argument [2021/06/03 12:25:11.037] [1622723111:37622][12363:0x7f7177fef700], file:wt.wt, txn-recover: __txn_op_apply, 288: operation apply failed during recovery: operation type 4 at LSN 2/2560: Invalid argument [2021/06/03 12:25:11.037] [1622723111:37689][12363:0x7f7177fef700], file:wt.wt, txn-recover: __wt_txn_recover, 1055: Recovery failed: Invalid argument [2021/06/03 12:25:11.042] [1622723111:42690][12363:0x7f7177fef700], connection: __wt_cache_destroy, 364: cache server: exiting with 8 pages in memory and 0 pages evicted [2021/06/03 12:25:11.042] [1622723111:42917][12363:0x7f7177fef700], connection: __wt_cache_destroy, 367: cache server: exiting with 4890 image bytes in memory [2021/06/03 12:25:11.042] [1622723111:42933][12363:0x7f7177fef700], connection: __wt_cache_destroy, 370: cache server: exiting with 15805 bytes in memory [2021/06/03 12:25:11.042] [1622723111:42940][12363:0x7f7177fef700], connection: __wt_cache_destroy, 376: cache server: exiting with 7566 bytes dirty and 2 pages dirt
We trigger this specific assertion error since the table has been created with the following configuration:
assert=(write_timestamp=on),write_timestamp_usage=always