Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-71218

Review test wrongly blacklisted because of [solved] SERVER-17397

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sharding EMEA

      There are many tests blacklisted in several suites because of SERVER-17397 that has been solved in v5.0. Such tests must be unblacklisted in order to increase the coverage because they're not supposed to fail anymore in sharded clusters.

      $ git grep SERVER-17397
      buildscripts/resmokeconfig/suites/concurrency_sharded_causal_consistency.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_causal_consistency_and_balancer.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_kill_primary_with_balancer.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_local_read_write_multi_stmt_txn.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_local_read_write_multi_stmt_txn_with_balancer.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_multi_stmt_txn.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_multi_stmt_txn_kill_primary.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_multi_stmt_txn_terminate_primary.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_multi_stmt_txn_with_balancer.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_multi_stmt_txn_with_stepdowns.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_replication.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_replication_with_balancer.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_terminate_primary_with_balancer.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_with_stepdowns.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      buildscripts/resmokeconfig/suites/concurrency_sharded_with_stepdowns_and_balancer.yml:  # SERVER-17397 Drops of sharded namespaces may not fully succeed
      jstests/concurrency/fsm_workloads/invalidated_cursors.js:                // still needs to be done, but these failures may be due to SERVER-17397 'drops in
      jstests/concurrency/fsm_workloads/invalidated_cursors.js:                // still needs to be done, but these failures may be due to SERVER-17397 'drops in
      
      

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: