-
Type: Build Failure
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
5
-
v4.4
make-check-test failed on RHEL 8.0
Host: ec2-100-26-173-3.compute-1.amazonaws.com
Project: WiredTiger (develop)
Commit: diff: WT-5469 Support mixing timestamped and non-timestamped updates (#5270)
- When inserting a non-timestamped update into the history store, we
should delete all history store records for that key to avoid
visibility issues.
- If we apply a non-timestamped tombstone on top of a timestamped value,
force the tombstone to be globally visible so the key gets deleted. We
can't have malformed cells where the stop pair is earlier than the start. | 21 Feb 20 07:01 UTC
Evergreen Subscription: ; Evergreen Event:
- is depended on by
-
WT-6180 Enable lower isolation levels in test_wt2323_join_visibility
- Closed
- is duplicated by
-
WT-5913 test/format assertion mod->mod_replace.addr != NULL
- Closed
- is related to
-
WT-5640 test_wt2323_join_visibility fail when processing consecutive tombstones in __wt_hs_insert_updates
- Closed
-
WT-6198 test_wt2323_join_visibility failed with WT_NOTFOUND
- Closed
-
WT-5985 Turn off format testing for relaxed isolation levels
- Closed
- related to
-
WT-6075 Re-enable csuite-wt2323-join-visibility-test
- Closed
-
WT-6186 Only delete timestamped history store entries when seeing a non-timestamped tombstone
- Closed