The jstests/libs/profiler.js library is providing some functions to check existence and number of occurrences of oplog entries.

Since retried idempotent operations are generating duplicate entries (as happened in BF-18868), this should be taken into account when calling profilerHasNumMatchingEntriesOrThrow and profilerHasSingleMatchingEntryOrThrow that are otherwise failing.

A possible solution would be adding two equivalent functions profilerHasSingleIdempotentMatchingEntr[y|ies]OrThrow deduplicating commands presenting the same fields (maybe it is enough to just check the tuple <namespace, command type, clusterTime>).