ExecutionApi: Retrieve to correct CAS directly

... by keeping track of each blob being a file or executable
and storing it to the correct local physical CAS directory.
The new flag is merely a hint and only used by the local
execution API. Leaving it out will still correctly transfer
the blob but may cause unnecessary duplicates in file CAS.

1 files changed, 2 insertions, 1 deletions

diff --git a/test/buildtool/execution_api/local/local_execution.test.cpp b/test/buildtool/execution_api/local/local_execution.test.cpp
index 14dad898..b695df1e 100755
--- a/test/buildtool/execution_api/local/local_execution.test.cpp
+++ b/test/buildtool/execution_api/local/local_execution.test.cpp
@@ -188,7 +188,8 @@ TEST_CASE_METHOD(HermeticLocalTestFixture,
 
     std::string test_content("test");
     auto test_digest = ArtifactDigest::Create<ObjectType::File>(test_content);
-    REQUIRE(api.Upload(BlobContainer{{BazelBlob{test_digest, test_content}}},
+    REQUIRE(api.Upload(BlobContainer{{BazelBlob{
+                           test_digest, test_content, /*is_exec=*/false}}},
                        false));
 
     std::string input_path{"dir/subdir/input"};