Major - P3 The timestamp-abort test program has an issue where it reports a failure (missing record) improperly. The failing output looks like:
Create 5 writer threads Thread 1 starts at 0 Thread 2 starts at 3689348814741910323 Thread 3 starts at 7378697629483820646 Thread 4 starts at 11068046444225730969 Thread 5 starts at 14757395258967641292 Checkpoint 0 complete. Minimum ts 1224 Checkpoint 1 complete. Minimum ts 2320 Parent: compatibility: false, in-mem log sync: false, timestamp in use: true Parent: Create 5 threads; sleep 10 seconds Kill child Open database, run recovery and verify content Stable: key 1 value 1 Stable: key 3 value 1762 Stable: key 4 value 156 Got stable_val 1762 records-2: COLLECTION no record with key 3689348814741910675 record ts 1766 <= stable ts 68702698616 records-2: COLLECTION no record with key 3689348814741910676 record ts 1771 <= stable ts 68702698616 records-2: COLLECTION no record with key 3689348814741910677 record ts 1776 <= stable ts 68702698616 records-2: COLLECTION no record with key 3689348814741910678 record ts 1781 <= stable ts 68702698616 records-2: COLLECTION no record with key 3689348814741910679 record ts 1786 <= stable ts 68702698616
This particular output is from http://build.wiredtiger.com:8080/job/wiredtiger-valgrind/2504/console
This is a test program issue. It didn't read a stable timestamp from the stable ts table for thread 2 and used an uninitialized value instead and therefore reported an error.