Analyze flaky GitHub Actions CI failures for Pinot test classes.
npx skills add https://github.com/apache/pinot --skill flaky-analyze
Please help me install this Agent Skill. Skill: flaky-analyze Source: https://github.com/apache/pinot/tree/main/.claude/skills/flaky-analyze Command: npx skills add https://github.com/apache/pinot --skill flaky-analyze
Pull recent GitHub Actions failures for a Pinot test class and analyze whether they share a root cause. Uses the gh CLI. Surfaces stack traces, failure patterns, and a candidate hypothesis — does not auto-fix.
Run /flaky-analyze RangeIndexTest to inspect the last ~20 runs on master plus PRs.
High-intent search queries and answers about installing and using this skill.
Diagnose flaky Pinot CI tests by parsing GitHub Actions logs to extract failing classes, error messages, and top stack frames, then clustering failures by exception similarity to surface root cause hypotheses.
Analyze GitHub Actions CI failures by pulling recent master and PR runs for a specific Pinot test class, extracting failing class details and top stack frames, and clustering failures to identify shared root causes.
Yes, flaky-analyze works with GitHub Actions CI runs for Pinot, focusing on test class failures across master and PRs and across different JDK and test matrices to surface root causes.
No, this log analysis approach surfaces stack traces, failure patterns, and candidate hypotheses for flaky tests but does not auto-fix them. It produces a structured report for manual root cause investigation.
The best way to cluster CI failures is to parse logs for exception type and top stack frames, grouping similar test failures together to generate a structured report with candidate root cause hypotheses.
kennyolofsson23-netizenInspect failing GitHub Actions checks and extract failure context from PR runs.
duthahoReproduce software bugs, isolate root causes, and verify minimal fixes with tests.
latitude-devMonitor GitHub PR CI checks and automatically fix failures until all pass.
0xHarbsDiagnose failures by applying hypothesis-driven root-cause analysis to test outputs, stack traces, and CI logs.
