Right now we have an unfortunate bifurcation in CI unit test execution between Windows and Linux/MacOS where we run Windows unit tests through resmoke instead of "bazel test" (separate task definition). This creates different log outputs, which are difficult to handle.

Revisit whether or not it's possible to run with "bazel test" / sandbox on windows without significantly increasing the risk of exceeding the 255 path length restrictions for data dependencies.