We currently do a build with configure --with-timestamp-size=0 as part of the wiredtiger-configure-combinations but don't run the Python test suite.
Some tests currently fail:
ERROR: test_prepare03.test_prepre03.test_prepare_cursor(table-row) (subunit.RemotedTestCase) test_prepare03.test_prepre03.test_prepare_cursor(table-row) ---------------------------------------------------------------------- _StringException: Traceback (most recent call last): File "/mnt/fast/mjc/wt/src/wiredtiger-git/test/suite/test_prepare03.py", line 93, in test_prepare_cursor self.session.prepare_transaction("prepare_timestamp=2a") WiredTigerError: Operation not supported ====================================================================== ERROR: test_las01.test_las01.test_las (subunit.RemotedTestCase) test_las01.test_las01.test_las ---------------------------------------------------------------------- _StringException: Traceback (most recent call last): File "/mnt/fast/mjc/wt/src/wiredtiger-git/test/suite/test_las01.py", line 149, in test_las self.conn.set_timestamp('stable_timestamp=' + timestamp_str(1)) WiredTigerError: Operation not supported ...
Those tests should be skipped when timestamps are disabled, we have wiredtiger.timestamp_build() to check that. We should also periodically run the unit test suite with that build to prevent regressions.