From 1e596d9ba2760305efff99d6d332d21603c16e28 Mon Sep 17 00:00:00 2001 From: Klaus Aehlig Date: Thu, 10 Apr 2025 15:18:21 +0200 Subject: 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. --- src/buildtool/execution_api/remote/bazel/bazel_ac_client.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src') 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); -- cgit v1.2.3