Import wiredtiger: af2cb8f052184a94635c3bfc358620dd36df5828 from branch mongodb-4.4

ref: 3818fb14bd..af2cb8f052
for: 4.3.1

WT-4972       Add new RHEL Evergreen build variant
WT-4975       Migrate Jenkins “wiredtiger-pull-request-asan” job to Evergreen
WT-5123       Fill multi-paragraph comments
WT-5150       LAS sweep is not removing the entries that are no longer required
WT-5161       Remove deprecated git.apply_patch
WT-5163       Fix ignored failure return in WT_CURSOR.next when random retrieval configured
WT-5164       Fix inconsistent underscore/dash output
WT-5166       Allow configuring configure flags in evergreen builds

1 files changed, 9 insertions, 12 deletions

diff --git a/src/third_party/wiredtiger/src/meta/meta_turtle.c b/src/third_party/wiredtiger/src/meta/meta_turtle.c
index e1289864c6c..80e409f380f 100644
--- a/src/third_party/wiredtiger/src/meta/meta_turtle.c
+++ b/src/third_party/wiredtiger/src/meta/meta_turtle.c
@@ -197,19 +197,16 @@ __wt_turtle_init(WT_SESSION_IMPL *session)
     WT_RET(__wt_remove_if_exists(session, WT_METADATA_TURTLE_SET, false));
 
     /*
-     * If we found a corrupted turtle file, then delete it and create a new.
-     * We could die after creating the turtle file and before creating the
-     * metadata file, or worse, the metadata file might be in some random
-     * state.  Make sure that doesn't happen: if we don't find the turtle
-     * file, first create the metadata file, load any hot backup, and then
-     * create the turtle file.  No matter what happens, if metadata file
-     * creation doesn't fully complete, we won't have a turtle file and we
-     * will repeat the process until we succeed.
+     * If we found a corrupted turtle file, then delete it and create a new. We could die after
+     * creating the turtle file and before creating the metadata file, or worse, the metadata file
+     * might be in some random state. Make sure that doesn't happen: if we don't find the turtle
+     * file, first create the metadata file, load any hot backup, and then create the turtle file.
+     * No matter what happens, if metadata file creation doesn't fully complete, we won't have a
+     * turtle file and we will repeat the process until we succeed.
      *
-     * Incremental backups can occur only if recovery is run and it becomes
-     * live. So, if there is a turtle file and an incremental backup file,
-     * that is an error.  Otherwise, if there's already a turtle file, we're
-     * done.
+     * Incremental backups can occur only if recovery is run and it becomes live. So, if there is a
+     * turtle file and an incremental backup file, that is an error. Otherwise, if there's already a
+     * turtle file, we're done.
      */
     WT_RET(__wt_fs_exist(session, WT_INCREMENTAL_BACKUP, &exist_incr));
     WT_RET(__wt_fs_exist(session, WT_INCREMENTAL_SRC, &exist_isrc));