From df4ac66b272d1e26df42855143dda79fc268b558 Mon Sep 17 00:00:00 2001 From: Klaus Aehlig Date: Thu, 6 Jun 2024 16:33:19 +0200 Subject: tc writing: allow different log level ... for failures instead of the binary strict_logging. In this way, we can log at log level Error in the serve instance, and for the client at level Warning or Info, depending on whether failure is expected (i.e., if targets are potentially taken from a serve endpoint) or not. --- src/buildtool/serve_api/serve_service/target.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/buildtool/serve_api/serve_service/target.cpp') diff --git a/src/buildtool/serve_api/serve_service/target.cpp b/src/buildtool/serve_api/serve_service/target.cpp index 9f54f7c3..3fc22c73 100644 --- a/src/buildtool/serve_api/serve_service/target.cpp +++ b/src/buildtool/serve_api/serve_service/target.cpp @@ -518,7 +518,7 @@ auto TargetService::ServeTarget( RemoteServeConfig::TCStrategy(), tc, &logger, - true /*strict_logging*/); + LogLevel::Error); if (build_result->failed_artifacts) { // report failure locally, to keep track of it... -- cgit v1.2.3