summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSergi Mateo Bellido <sergi.mateo-bellido@mongodb.com>2021-04-29 12:57:52 +0000
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2021-05-03 08:12:23 +0000
commitdd29a74baf3d22d81feae48748217e39586e522b (patch)
tree03a3eb715d6a557770d4a1a2e51031705d52a14d
parenta56d19b3cd567c1fed816f75f358b72fcb88841b (diff)
downloadmongo-dd29a74baf3d22d81feae48748217e39586e522b.tar.gz
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.
-rw-r--r--jstests/libs/read_write_concern_defaults_propagation_common.js8
1 files changed, 0 insertions, 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;
},