No-op retries are recorded in system.profile, for the top command, and for opcounters, which causes jscore tests with no-op retries of retryable writes to fail, because the number of recorded commands is higher than the number sent explicitly by the test. It should be determined if these metrics should ignore retries, or if this is the desired behavior.

Failing retryable_writes_jscore_passthrough tests:

• operation_latency_histogram.js
• views_stats.js
• top.js
• profile2.js
• profile3.js
• profile_findandmodify.js