RFC for E2E test failure triage agent - #152
Draft
or4dx wants to merge 1 commit into
Draft
Conversation
or4dx
marked this pull request as draft
June 30, 2026 16:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the first draft of the failure triage agent RFC that details a service that triages failed E2E test runs. It gathers context from mcp-kubernetes and crust-gather. It uses an LLM to classify each failure, route it to the right team, and create issues or Slack alerts. The work ships in phases. Each phase produces value on its own. We can kill the project at any phase if it stops paying off.