tree b1d15b114c0f25563cb78633e19aabea98c4c550
parent e764670427e526c01c4ca5b44b5e23120ed4b73d
author lberki <lberki@google.com> 1564651734 -0700
committer Copybara-Service <copybara-worker@google.com> 1564651790 -0700

Remove {OutputStore,ActionExecutionValue}.additionalOutputData.

Instead of having another map, when additional data is needed, replace artifactData with it.

There was one place where we exploited the difference between the two: for cases where we get a digest from remote execution but one is not available for the file system, FilesystemValueChecker used only one map.

I fixed this by adding a method to FileArtifactValue that tells whether given two instances, Blaze should assume that there was no change and replicated the existing behavior as faithfully as possible.

RELNOTES: None.
PiperOrigin-RevId: 261086332