Hi all, I work on the remote-apis-testing project and we've been getting test failures with Pants recently, after updating to a newer version. It seems to have happened between 2.4.1rc1 and 2.5.0rc2. @fast-nail-55400 has raised an issue: https://github.com/pantsbuild/pants/issues/12157. I was wondering if anyone had any insight? The problem seems to happen when the pants client sends a remote execution request to execute a

./bin/protoc

command. For each server that we test against, we get an error that says

not found

or

no such file or directory

.

Thanks for that commit range. By inspection of that range it looks like https://github.com/pantsbuild/pants/pull/11867 must be it. That commit does work with Pants local execution sandboxing; so it looks like our local execution sandboxing must be non-conforming to the REAPI: https://github.com/Eric-Arellano/pants/blob/73026b127afff270e63f0fb92501c5d188ab1ebb/src/rust/engine/process_execution/bazel_protos/protos/bazelbuild_remote-apis/build/bazel/remote/execution/v2/remote_execution.proto#L574 I'll update the issue and take a swing at this later this morning.