From dd29a74baf3d22d81feae48748217e39586e522b Mon Sep 17 00:00:00 2001
From: Sergi Mateo Bellido <sergi.mateo-bellido@mongodb.com>
Date: Thu, 29 Apr 2021 12:57:52 +0000
Subject: SERVER-54834 Read write concern defaults propagation jstests should
 not assert on wall clock times

Even if all host run on the same machine, we cannot compare wall clock
times because some implementations are not monotonic. Thus, even if we
get one time before another one, it might happen that the first one is
not smaller or equal than the second one.
---
 jstests/libs/read_write_concern_defaults_propagation_common.js | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/jstests/libs/read_write_concern_defaults_propagation_common.js b/jstests/libs/read_write_concern_defaults_propagation_common.js
index 22167cd48f3..474a9828af0 100644
--- a/jstests/libs/read_write_concern_defaults_propagation_common.js
+++ b/jstests/libs/read_write_concern_defaults_propagation_common.js
@@ -100,14 +100,6 @@ var ReadWriteConcernDefaultsPropagation = (function() {
                             return false;
                         }
                     }
-
-                    // localUpdateWallClockTime reflects which the conn updated its cache.  Since
-                    // all the conns (including setConn) are running on a single host, we can check
-                    // that this is later than when setDefaultRWConcern was run.
-                    if (!(connDefault[kLocalUpdateWallClockTimeField] >=
-                          connDefault[kUpdateWallClockTimeField])) {
-                        return false;
-                    }
                 }
                 return true;
             },
-- 
cgit v1.2.1