The SecondarySetWildcardIndexMultikeyOnInsert test case tries to "coerce" the oplog batch writer into interleaving operations in a certain way:
Unfortunately, the batch applier splits up operations across many threads based on a hash of _id and a runtime-randomized seed, so this coercion is fruitless. If op1 and op2 end up in the same batch, they will be inserted in the same transaction, which will return this error from WiredTiger: "commit timestamp <op1> older than the first commit timestamp <op2>", and trigger this fatal assertion in MongoDB.
This test needs to be rewritten so that it does not batch out-of-order operations together or depend on thread synchronization.
Bonus! Because of the way the hash seed is randomized to split up operations to 16 different threads, the probability of this test putting op2 and op1 in the same batch is 1/16. So theoretically this test will fail 6.25% of the time it is run.