migration_with_source_ops.js is currently blacklisted in the new sharding_last_stable_mongo_and_mixed_shards suite. This is because a 3.2 shard cannot set a failpoint it does not have, which the 3.4 JS test calls.

3.4 migration_with_source_ops.js exercises two points in the code with the same failpoint, whereas in 3.2 migration_with_source_deletes.js only exercises one of those point. If the name of the failpoint were the same, the test could run, if only be 50% effective failpoint-wise with a 3.2 shard – it does nothing incorrect.