This test is currently failing 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

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 "bazel test --config=evg --linkstatic=False --strategy=TestRunner=remote +index_builds_test"

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