SERVER-137093ClosedFixed

Exclude change_stream_update_lookup_too_many_matching_documents.js from sharding_csrs_continuous_config_stepdown

The suite steps down the config server primary every 8 seconds. The test calls waitForClusterTime, which runs _configsvrGetHistoricalPlacement against the config primary (jstests/libs/query/change_stream_util.js:1509). If the call lands during a stepdown, the command returns an error with no historicalPlacement field. The helper then throws can't access property "status", ... historicalPlacement is undefined.

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
9.1.0-rc09.0.9
Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.