This test uses causally consistent connections, which sends all read requests with an afterClusterTime argument once a clusterTime has been returned to the shell. Previously, this test relied clusterTime not being propagated in FCV 3.4, but SERVER-32463 removed causal consistency FCV checks from master, so now afterClusterTime is being sent by the master nodes and is rejected by 3.6 nodes because they both still default to FCV 3.4. Once the default FCV has been raised to 3.6, this test should be safe to run in this suite in master.

The test also uses standalone shards, which can't accept afterClusterTime, so this test may need to wait until ShardingTest defaults to 1 node replica sets as well.

This blacklist may need to be backported to 3.6, since it seems that the test relies on the guarantees of causal consistency, which shouldn't have been provided by a cluster in FCV 3.4.