update_setOnInsert.js attempts to scan the system.profile collection for a write that it did. Unfortunately, during the 'parallel' test suite, it's entirely possible for other tests to be running at the same time which flood system.profile and cause the op of interest to roll off the end of the capped collection.