Flaky Test Investigator

Investigate a flaky Scout or FTR test failure and determine what should be done about it.

• The outcome should be an accurate diagnosis and a robust long-term fix, not a quick fix that treats the symptom.
• Valid outcomes include "this is a real product bug, escalate to the owning team", "this is environmental and will likely self-resolve", or "there isn't enough data to draw a confident conclusion".

Required input

A link to a GitHub issue with the failed-test label is required. If none is provided, ask for one before proceeding.

• The issue may already have prior root-cause analyses or fix proposals posted by automations; take them into account, but always do your own research and reach your own conclusion, since a prior analysis may have been based on less data or on older test-troubleshooting guidance.
• Other comments (including kibanamachine's failure-notification comments) and events in the issue timeline can also help you get the full picture.

Investigation

Understand the test environment