-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Checkpoints, Test Python
-
5
-
StorEng - Defined Pipeline
This ticket arose as a part of fixing WT-9902. In WT-9902, the original scenario that had been disabled via @wttest.skip_for_hook("timestamp", ...) went away and that ticket was closed. However, there are two scenarios detailed there, and the skip for tiered hooks is resulting in test_checkpoint01.py failing with:
====================================================================== FAIL: test_checkpoint01.test_checkpoint_target.test_checkpoint_target -s 1 (table) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/ubuntu/wt/git/wt-9890-timestamp-hook/test/suite/wttest.py", line 386, in _callTestMethod method() File "/home/ubuntu/wt/git/wt-9890-timestamp-hook/test/suite/test_checkpoint01.py", line 252, in test_checkpoint_target self.check(self.uri + '1', ds1, 'UPDATE') File "/home/ubuntu/wt/git/wt-9890-timestamp-hook/test/suite/test_checkpoint01.py", line 218, in check self.assertEquals(cursor[ds.key(10)], value) AssertionError: 'ORIGINAL' != 'UPDATE' - ORIGINAL + UPDATE
To reproduce, remove the skip_for_hook annotation in test_checkpoint01.py and run with the tiered --hook.
~/wiredtiger/build$ python3 ../test/suite/run.py -v 2 --hook tiered test_checkpoint01
- related to
-
WT-12494 Checkpoint target option: remove documentation and close old tickets
-
- Closed
-