-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
ALL
-
v3.4
-
Query 2017-03-06
-
0
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