Minor - P4 Steps to reproduce:
1. Build as follows with a large timestamp (say with timestamp size 16):
CFLAGS="-ggdb" ../configure --enable-python --enable-strict --enable-diagnostic --enable-verbose --disable-static --with-timestamp-size=16; make -j20
2. Run the python test test_timestamp01:
The following portion of the test fails:
# Too big is also not permitted
self.session.begin_transaction()
self.assertRaisesWithMessage(wiredtiger.WiredTigerError,
lambda: self.session.commit_transaction(
'commit_timestamp=' + timestamp_str(1 << 100)),
'/too long/')
With 16 bit timestamp size, 1 << 100 is not too long. The test should look at WT_TIMESTAMP_SIZE when deciding what is too long. I am not sure how to pass that value into the python test.