summaryrefslogtreecommitdiff
path: root/buildscripts
diff options
context:
space:
mode:
authorJudah Schvimer <judah@mongodb.com>2020-06-01 19:02:23 -0400
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2020-06-17 15:57:44 +0000
commite5a25068d1e122488ea5e8d400e86e96022e4c72 (patch)
tree98785d27c3669e2dd3ac2859ad3ff08c87606efb /buildscripts
parentf5b36d71a86cf3c46a32b9d2eb109b6ec760b512 (diff)
downloadmongo-e5a25068d1e122488ea5e8d400e86e96022e4c72.tar.gz
SERVER-48527 Aborting in-progress transactions on step-up should clear session state before returning
(cherry picked from commit 07169364c2aece0fb99f4a97b796196edb033efa)
Diffstat (limited to 'buildscripts')
-rw-r--r--buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml1
1 files changed, 1 insertions, 0 deletions
diff --git a/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml b/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml
index 4be1df1d525..49d61358cc9 100644
--- a/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml
+++ b/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml
@@ -134,6 +134,7 @@ selector:
- jstests/sharding/mongos_no_replica_set_refresh.js
- jstests/sharding/movechunk_interrupt_at_primary_stepdown.js
- jstests/sharding/primary_config_server_blackholed_from_mongos.js
+ - jstests/sharding/refine_collection_shard_key_abort_on_stepup.js
# Nothing is affected by config server step down
- jstests/sharding/basic_sharding_params.js
# ShardingTest is never used, so continuous step down thread never starts