Description of the problem:

I ran into a weird error when running a test through Bazel RBE on Windows. There is the issue describing it in detail. Its summary is that SymInitialize (Windows Debug API) fails only when the length of the target is 89 or 90. When the target name is shortened or lengthened, this issue is fixed. So something related to the length should be there.

This is a PR to reproduce this simply and I haven't seen this problem when running Bazel directly on Windows. The Bazel RBE team investigated this problem and this might be a result of combination of bazel and docker so I like to get help from the Bazel team.

I guess changing the threshold (from 260 to 258) to use shortened paths on Windows can fix this issue. code

Internal bug with details: b/169902891

Feature requests: what underlying problem are you trying to solve with this feature?

SymInitialize failed only when the length of path is 89 and 90

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

grpc/grpc#24302

What operating system are you running Bazel on?

Windows server 2016

What's the output of bazel info release?

I cannot run bazel info but the version of bazel is 2.2.0.