Custom RBE timeout for non-test actions #21142
Labels
P2
We'll consider working on this in future. (Assignee optional)
team-Remote-Exec
Issues and PRs for the Execution (Remote) team
type: feature request
Description of the feature request:
RBE action timeouts for test actions can be increased using the
--test_timeout
flag, otherwise the default timeout for RBE actions is one hour.Bazel can already request a different timeout from RBE (read from execution info here, into SpawExecutionContext here, and into the remote action builder here), but there is no API to do so for non-test actions. My dirty fix at the moment is this + setting a timeout in the
execution_requirements
of thectx.actions.run
call. It works, though I suspect it would break anyone using "timeout" as a tag in their rule (this could be worked around by maintaining 2 separate lists for tags specified in target definitions vsexecution_requirements
specified from actx.actions.run
call).More generally it seems the list of exec_info keys that we let users specify is intentionally short, so filing this as a feature request in case my approach has unintended consequences I haven't thought of.
Which category does this issue belong to?
Remote Execution
What underlying problem are you trying to solve with this feature?
No response
Which operating system are you running Bazel on?
No response
What is the output of
bazel info release
?No response
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
Have you found anything relevant by searching the web?
#12349 would likely be solved by this.
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: