sql, test: automate test failure analysis (phase one - manual input)

[eric-alton]

Summary

Each week members of the SQL Foundations team meet to manually triage new C-test-failure issues. This process involves manually navigating through each issue to the corresponding logs, identifying the failing statement, error, and any other related information, then making a judgement call which typically results in closing the issue or assigning it to an individual for further analysis.

This issue tracks developing an AI skill for automating the analysis once a human operator manually collects the logs and places them in an accessible location. Follow-up issues will build on this to have the AI agent automatically access the log files needed for analysis, as well as take action on issues with clear next steps (ie reassignment).

Details

Develop an AI skill which will analyze a test failure when provided as input the C-test-failure issue and relevant logs. At a minimum the analysis should contain:

• The failing statement
• The error encountered
• Any related context such as a call stack
• The last time the test was modified
• Analysis which suggests next steps, for example close as duplicate, reassign to another team, and/or a suggested fix

These details should be posted to the issue as a comment which indicates they are the result of the AI analysis.

Epic: CRDB-60540

Jira issue: CRDB-60541