tree 3864b9792640a12dbecde34d743ed6e5a7578c3a
parent 9f9f5ec10fed81362c35c50eeb4515bbe5bf8bce
author mschaller <mschaller@google.com> 1573844046 -0800
committer Copybara-Service <copybara-worker@google.com> 1573844110 -0800

Refactor lost input ownership calculation, do it unconditionally

Previously, lost input ownership information from an action's inputDeps
was only calculated if any lost inputs came from runfiles. By
calculating ownership information unconditionally, lost input owners can
be determined for each kind of aggregating artifact, except for filesets,
at the ActionExecutionFunction level.

By not treating runfiles ownership specially, ActionRewindStrategy's
lost-input-owning direct deps calculation can be simpler. Also, the
runfiles-specific tracking in LostInputsExecException.InputOwners is no
longer necessary, so it can be eliminated in favor of the now-equivalent
ActionInputDepOwners.

This CL also makes LostInputs{ExecException,ActionExecutionException}
independent. That allows other parts of action execution, besides those
which throw ExecExceptions, to be able to communicate lost input
failures. Now that the ActionExecutionFunction level calculates lost
input ownership unconditionally, the requirements for those parts is
looser. Before, they would have been responsible for determining all
ownership relations except for those from runfiles. Now, they're
responsible only for determining ownership relations from filesets.

RELNOTES: None.
PiperOrigin-RevId: 280692324