Change stream tests make invalid assumptions about thread scheduling on the server, or, more precisely, about valid responses to getMore command on cursors on change stream cursors.
Actually, it is valid for the server to return zero results on a change stream cursor even if there are change events available at the moment. It can happen in case when the reading thread on the server does not get enough time allocated and the timeout on the change stream cursor (command "getMore") expires (1 second by default).
The test and the location that failed: https://github.com/10gen/mongo/blob/acdc463fe60bdc85aeced25297041b4051a0fc33/jstests/noPassthrough/report_post_batch_resume_token_mongod.js#L36.
Likely, one of the places where that assumption is made is at https://github.com/10gen/mongo/blob/acdc463fe60bdc85aeced25297041b4051a0fc33/src/mongo/shell/query.js#L845-L851.