Critical - P2 The smoke test of the timestamp_abort program failed one of the Evergreen tests. The test case that failed is: ./test_timestamp_abort -m -t 10 -T 5. One of the threads shows missing records in the middle of its range:
[2017/10/19 12:16:15.080] Parent: compatibility: false, in-mem log sync: true, timestamp in use: true [2017/10/19 12:16:15.080] Parent: Create 5 threads; sleep 10 seconds [2017/10/19 12:16:15.122] Kill child [2017/10/19 12:16:15.122] Open database, run recovery and verify content [2017/10/19 12:16:15.122] Stable: key 5 value 317257 [2017/10/19 12:16:15.122] Got stable_val 317257 [2017/10/19 12:16:15.122] records-4: COLLECTION after absent records 14757395258967677166-14757395258967680761 key 14757395258967680762 exists [2017/10/19 12:16:15.122] records-4: COLLECTION after absent records 14757395258967677166-14757395258967680761 key 14757395258967680763 exists [2017/10/19 12:16:15.122] records-4: COLLECTION after absent records 14757395258967677166-14757395258967680761 key 14757395258967680764 exists [2017/10/19 12:16:15.122] records-4: COLLECTION after absent records 14757395258967677166-14757395258967680761 key 14757395258967680765 exists ... [2017/10/19 12:16:29.025] records-4: COLLECTION after absent records 14757395258967677166-14757395258967680761 key 14757395258967708212 exists [2017/10/19 12:16:29.025] records-4: COLLECTION after absent records 14757395258967677166-14757395258967680761 key 14757395258967708213 exists