-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Disagg CI-blocker
-
None
-
Storage Engines, Storage Engines - Transactions
-
SE Transactions - 2025-09-12
-
3
When running test_timestamp08.py with disagg hook, an assertion was raised getting an unexpected timestamp for the all_durable query before transaction commit. (scenario 2):
======================================================================
[pid:6625]: FAIL: None
----------------------------------------------------------------------
[pid:6625]: Traceback (most recent call last):
File "/home/ubuntu/work/wiredtiger/test/suite/wttest.py", line 243, in _callTestMethod
method()
File "/home/ubuntu/work/wiredtiger/test/suite/test_timestamp08.py", line 265, in test_all_durable
self.assertTimestampsEqual(self.conn.query_timestamp('get=all_durable'), self.timestamp_str(9))
File "/home/ubuntu/work/wiredtiger/test/suite/wttest.py", line 734, in assertTimestampsEqual
self.assertEqual(int(ts1, 16), int(ts2, 16))
AssertionError: 0 != 9
The command to reproduce the failure:
$ python3 ../test/suite/run.py -v 2 --hook disagg test_timestamp08.py
- related to
-
WT-14786 Disagg python testing: triage test_timestamp*.py tests
-
- In Progress
-