From fffee539ec37e9e68189e71994aa2c901d30c9fb Mon Sep 17 00:00:00 2001 From: Klaus Aehlig Date: Mon, 28 Feb 2022 10:59:29 +0100 Subject: main: add a log message after finishing analysis In this way, the user has a slightly better insight into the stage the tool currently works on. While there, also move the first report of taintedness to the earliest possible moment. --- src/buildtool/main/main.cpp | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'src') diff --git a/src/buildtool/main/main.cpp b/src/buildtool/main/main.cpp index 74d75d56..d1343ad5 100644 --- a/src/buildtool/main/main.cpp +++ b/src/buildtool/main/main.cpp @@ -1257,6 +1257,10 @@ auto main(int argc, char* argv[]) -> int { return kExitSuccess; } #ifndef BOOTSTRAP_BUILD_TOOL + Logger::Log(LogLevel::Info, + "Analysed target {}", + result->id.ToString()); + ReportTaintedness(*result); auto const& [actions, blobs, trees] = result_map.ToResult(); // Clean up result map, now that it is no longer needed @@ -1270,7 +1274,6 @@ auto main(int argc, char* argv[]) -> int { "{}ing {}.", arguments.cmd == SubCommand::kRebuild ? "Rebuild" : "Build", result->id.ToString()); - ReportTaintedness(*result); auto build_result = traverser.BuildAndStage( artifacts, runfiles, actions, blobs, trees); -- cgit v1.2.3