Details
Description
The backup_cursor_truncate_after test will always try setting the truncate after point to the top of oplog. However, that timestamp is "inclusive" meaning replication recovery will try to remove that document. If that oplog entry is also the checkpoint timestamp, that document is majority committed and cannot be removed. The test should omit that scenario when it occurs.