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

ensure or enforce that ShardingTest.stop() is called in all tests that start a ShardingTest

    XMLWordPrintable

    Details

      Description

      The check that UUIDs are consistent across a cluster was placed in ShardingTest.stop() under SERVER-30511.

      It was intended to provide passthrough coverage that UUIDs are always consistent in a cluster, by running at the end of every test that starts a ShardingTest.

      However, only tests that actually call ShardingTest.stop() will perform the check.

      Should we:

      • audit all jstests to ensure they call ShardingTest.stop() if they start a ShardingTest
      • place some kind of lint or compile check to ensure any future tests call ShardingTest.stop() if they start a ShardingTest?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-tig DO NOT USE - Backlog - Test Infrastructure Group (TIG)
              Reporter:
              esha.maharishi Esha Maharishi
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: