Fix db_s_config_server_test remote test compatibility

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • ALL
    • Hide

      bazel test --strategy=TestRunner=remote +
      db_s_config_server_test

      Show
      bazel test --strategy=TestRunner=remote + db_s_config_server_test
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This test is currently failing to be run in EngFlow remote execution because it's creating a temporary directory in the root of the filesystem, which breaks hermetic execution guarantees:

      {"t":\{"$date":"2025-08-26T01:11:02.027+00:00"}

      ,"s":"I", "c":"TEST", "id":23065, "svc":"-", "ctx":"main","msg":"Totals","attr":{"totals":{"name":"TOTALS","tests":556,"fails":1,"time":

      {"durationMillis":116260}

      ,"failures":[{"test":"SamplingSucceedsWithLimitedMemoryForSortOperation","type":"std::exception","error":"boost::filesystem::create_directories: Permission denied [system:13]: \"/data/db/_tmp\", \"/data\""}]}}}
      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 --strategy=TestRunner=remote +
      db_s_config_server_test"
      Please ask in #ask-devprod-build if you run into any issues

            Assignee:
            Adi Zaimi
            Reporter:
            Zack Winter
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: