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, 2 deletions

diff --git a/test/buildtool/execution_api/bazel/bazel_cas_client.test.cpp b/test/buildtool/execution_api/bazel/bazel_cas_client.test.cpp
index 1081c952..8b81307b 100644
--- a/test/buildtool/execution_api/bazel/bazel_cas_client.test.cpp
+++ b/test/buildtool/execution_api/bazel/bazel_cas_client.test.cpp
@@ -33,7 +33,7 @@ TEST_CASE("Bazel internals: CAS Client", "[execution_api]") {
         auto digest = ArtifactDigest::Create<ObjectType::File>(content);
 
         // Valid blob
-        BazelBlob blob{digest, content};
+        BazelBlob blob{digest, content, /*is_exec=*/false};
 
         // Search blob via digest
         auto digests = cas_client.FindMissingBlobs(instance_name, {digest});
@@ -65,7 +65,7 @@ TEST_CASE("Bazel internals: CAS Client", "[execution_api]") {
         faulty_digest.set_size_bytes(4);
 
         // Faulty blob
-        BazelBlob faulty_blob{faulty_digest, content};
+        BazelBlob faulty_blob{faulty_digest, content, /*is_exec=*/false};
 
         // Search faulty digest
         CHECK(cas_client.FindMissingBlobs(instance_name, {faulty_digest})