Help us understand the severity of this issue

• breakage; unable to contribute or trigger builds will no workarounds
• inconvenient workarounds exist, but significant effort required
• needed for a Flutter team-wide priority (already agreed upon)
• nice-to-have; none of the above

What do you need help with

Flutter's CI logs are often very verbose and difficult to visually parse. It can be difficult to identify what test failed and why it is failing.

To improve this, perhaps we could add functionality that make it easy to use Gemini to parse the logs for us. It would be nice if Gemini could tell us what test is failing, why it is failing, and where to find the failing test in Flutter's codebase.

To limit API usage, perhaps it can be a button that people can click rather than something automatic.