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

Tests that call getLatestProfilerEntry() should be blacklisted from dynamic initial sync passthrough suites

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.6, 3.5.4
    • Testing Infrastructure
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Query 2017-03-06
    • 0

    Description

      Any test that calls getLatestProfilerEntry() in the "dynamic" initial sync passthrough suites is almost certainly broken. The test expects to see the most recent operation it ran in the profiler, but sometimes it will see an operation performed by the downstream syncing node instead. We should blacklist all tests that call getLatestProfilerEntry() from the "dynamic" initial sync passthrough suites.

      The "dynamic" initial sync passthrough suites are the passthrough suites that use the hook BackgroundInitialSync. These include:
      replica_sets_initsync_jscore_passthrough
      replica_sets_resync_jscore_passthrough

      The tests in core that call getLatestProfilerEntry() are:
      jstests/core/profile_agg.js
      jstests/core/profile_count.js
      jstests/core/profile_delete.js
      jstests/core/profile_distinct.js
      jstests/core/profile_find.js
      jstests/core/profile_findandmodify.js
      jstests/core/profile_geonear.js
      jstests/core/profile_getmore.js
      jstests/core/profile_group.js
      jstests/core/profile_insert.js
      jstests/core/profile_mapreduce.js
      jstests/core/profile_update.js

      Attachments

        Activity

          People

            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: