The fsync_deadlock.js test must be removed from the sharding_csrs_continuous_config_stepdown suite because the timing of the fsyncLock request (which takes a Global S lock) may interfere with the RSTL Global X lock that is required for replication set state changes causing the test to hang.