This test is currently failing to be run in EngFlow remote execution. It's unclear to me why it's failing, but the main differences that will cause failures are 1. slightly different host resources are available (less ram/cpu) 2. containerization (if the test depends on kernel details this can cause issues) 3. external network access, which is disabled by default in remote execution.

This test only has compatibility issues with remote execution under the GCC Debug variant, so there could be an underlying timing issue that switching to remote test is triggering. This is especially likely since the issue doesn't happen consistently.

Once this is fixed, please remove the tag "incompatible_with_bazel_remote_test" from the test definition as well as the incompatibility select statement.

This is currently preventing us from switching all unit tests over to be run in remote execution, slowing down CI runs and costing several thousand dollars in infra spend a month.

To reproduce the issue, run the following (20x runs since it's inconsistent):

bazel test --verbose_failures --config=remote_test --config=evg --linkstatic=False --test_tag_filters=mongo_unittest,-intermediate_debug,-incompatible_with_bazel_remote_test --build_tag_filters=mongo_unittest,-incompatible_with_bazel_remote_test --test_timeout=600 --dbg=True --opt=on --build_otel=True --build_enterprise=False --jobs=800 --linkstatic=False --define=MONGO_VERSION=8.3.0-alpha0-870-g54a170d-patch-68b775736d3299000713a644 --remote_download_outputs=toplevel src/mongo/db/s:db_s_resharding_test --runs_per_test 20

Please ask in #ask-devprod-build if you run into any issues