BazelAcClient: log cache misses at trace level

... instead of at debug. We expect actions to be not in cache, so the fact
that we experience cache misses is not surprising. Given the information
available at this point, a useful logging indicating (in terms meaningful
to the user) is not possible. Therefore, keep the debug-level log clean.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/buildtool/execution_api/remote/bazel/bazel_ac_client.cpp b/src/buildtool/execution_api/remote/bazel/bazel_ac_client.cpp
index f6612377..221537f2 100644
--- a/src/buildtool/execution_api/remote/bazel/bazel_ac_client.cpp
+++ b/src/buildtool/execution_api/remote/bazel/bazel_ac_client.cpp
@@ -62,7 +62,7 @@ auto BazelAcClient::GetActionResult(
     if (not ok) {
         if (status.error_code() == grpc::StatusCode::NOT_FOUND) {
             logger_.Emit(
-                LogLevel::Debug, "cache miss '{}'", status.error_message());
+                LogLevel::Trace, "cache miss '{}'", status.error_message());
         }
         else {
             LogStatus(&logger_, LogLevel::Error, status);