Enhance Feedback Mechanism for local-pr-precheck command

[Matejkob]

Description

Background

Following the resolution of issue #2066, we have a comprehensive script that automates the verification process for changes made to the repository, including running various unit tests, building projects, and executing formatters. This automation ensures that modifications do not adversely affect the repository's integrity and functionality. However, the current output from this automation script is quite verbose, making it challenging to quickly identify the status of each check, especially in the context of numerous unit tests producing extensive logs.

Proposal

I propose we enhance the script's feedback mechanism to provide more concise and informative logs that clearly indicate the success or failure of each step in the automation process. This enhancement will make it easier for contributors to identify and address issues promptly, improving the efficiency of the development workflow.

Suggested Improvements

1. Summarized Output: Implement a summarization feature in the script that collates the results from each step (e.g., code generation, unit tests for different packages, building projects) and presents a consolidated report at the end. This report should highlight the overall success or pinpoint exactly what failed, such as which unit test(s), code generation step, or build process encountered issues.

2. Error Detailing: For steps that fail, provide a detailed output that includes not just the fact that it failed, but also specific information about what caused the failure. This could include the name of the failing test, the expected vs. actual outcome, or the error message from a build failure.

3. Automated Suggestions: Where possible, include automated suggestions or common fixes for identified issues. This could help contributors quickly resolve common problems without needing to dig deeply into the logs.

[ahoppen]

Tracked in Apple’s issue tracker as rdar://123190895