The ChangeStreamTest.assertChangeStreamThrowsCode function expects to see a specific error code upon starting a change stream, but it only runs the initial aggregate and a single getMore before giving up. In a sharded cluster, it is conceivable that the exception will not be seen on the first getMore. We should run getMore in an assert.soon loop to ensure that we do not produce any false negatives.