summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSamy Lanka <samy.lanka@mongodb.com>2019-02-20 19:19:30 -0500
committerSamy Lanka <samy.lanka@mongodb.com>2019-03-04 15:13:30 -0500
commit8ee639f4e80a24a60984502bb93ddb2caddade81 (patch)
tree5e1469e344611b3a7c88dd2ed3c5e7c297837464
parent1c24972a20f0cd5e37bb24648fffb3b1c7409f6f (diff)
downloadmongo-8ee639f4e80a24a60984502bb93ddb2caddade81.tar.gz
SERVER-39641 Blacklist max_time_ms.js from read concern linearizable passthrough
(cherry picked from commit fff6fcea7d72afd0583c8ba4bdbce094f80d7574) (cherry picked from commit be6ea4b3c4fb945f47b881bb5c5ffce7952dc018)
-rw-r--r--buildscripts/resmokeconfig/suites/read_concern_linearizable_passthrough.yml3
1 files changed, 3 insertions, 0 deletions
diff --git a/buildscripts/resmokeconfig/suites/read_concern_linearizable_passthrough.yml b/buildscripts/resmokeconfig/suites/read_concern_linearizable_passthrough.yml
index acd22fef685..bae6f9ba75d 100644
--- a/buildscripts/resmokeconfig/suites/read_concern_linearizable_passthrough.yml
+++ b/buildscripts/resmokeconfig/suites/read_concern_linearizable_passthrough.yml
@@ -14,6 +14,9 @@ selector:
# fsync.js runs the {fsync: 1, lock: 1} command, which prevents a linearizable read from writing
# an entry to the oplog.
- jstests/core/fsync.js
+ # This test uses a very short timeout for a read that becomes unreliable with read concern
+ # linearizable.
+ - jstests/core/max_time_ms.js
exclude_with_any_tags:
##
# The next three tags correspond to the special errors thrown by the