George Gensure

On the newly created wiki page https://github.com/bazelbuild/bazel-buildfarm/wiki/ExecutionPolicies - I'm sure it's woefully inadequate to describe this in detail, let me know what will fill in the blanks.

If it is running on the correct worker, just not with the wrapper, try removing the `name: "run"` line. That will make the policy a default one, with no name,...

--run_under is definitely a workaround, but the policy application occurs for named (non-default) policies when an action, through its command, specifies a platform property as you've indicated, with `name: "execution-policy",...

We're definitely lacking in docs in this area, we have some brief mentions of ExecutionPolicies in Worker docs, but that can be expanded.

Yup, that's an outstanding issue, and the indications from the bazel team are that my PR won't be accepted as is, since they preferred to create an `exec_groups` mechanism for...

Unfortunately we don't know the mnemonic on the buildfarm side, but the detection of execution 'types' according to a build system heuristic (recognizing tests, or even compiles as you've done...

The exec_groups code appears to have been completed upstream, which should allow full specification of the platform by sub-action type. If there are additional cases that appear to be uncovered...

Hm, https://github.com/werkt/bazel-buildfarm/tree/write-cancel-completion has a possible fix for this - we're essentially waiting for previous writes (which will include a UUID, presumably from a single client) to complete. There exists the...

> Thanks for reporting this. I have the same issue and I regret not addressing sooner. Our current deployment actually comments out lines 156 - 158: > > ``` >...

The validation procedure for your execution is attempting to observe the entire input tree of directories and ensure that they are present before scheduling the execution on a worker. It...