The analyze_shard_key_jscore_passthrough suite implicitly shards collections, which can cause some spurious timeout errors due to shard refreshes as seen in BF-30878. A similar issue does not seem to affect sharded_jscore_txns_sharded_collections, though it's not clear to me why that is.