Work directory should be added automatically as an input directory about bazel-buildfarm HOT 3 OPEN

I'll comment here and on the reclient bug, thanks for filing it:

From remote_execution.proto on the remote-apis repository:
https://github.com/bazelbuild/remote-apis/blob/1f36c310b28d762b258ea577ed08e8203274efae/build/bazel/remote/execution/v2/remote_execution.proto#L689-L692

  // The working directory, relative to the input root, for the command to run
  // in. It must be a directory which exists in the input tree. If it is left
  // empty, then the action is run in the input root.
  string working_directory = 6;

This is pretty clear to me that the working directory must be present in the input tree to meet the API's requirements, and that is down to the client's presentation.

from bazel-buildfarm.

add out\Release\args.gn as your inputs
like:
rewapper -inputs "out\Release\args.gn" clang.exe xxxxxxx
or:
rewapper -input_list_paths "xxxx.rsp" clang.exe xxxxxxx
xxxx.rsp:
out\Release\args.gn (your working_directory's args.gn)

from bazel-buildfarm.

Won't really work unless at least three, possibly several more, Chromium GN toolchain files are patched to change the arguments of the rewrapper command, since the path cannot be added to the rewrapper config file, which is used for multiple out/foo directories (our default dirs are out/Debug and Out/Release).

from bazel-buildfarm.