shiro_analyze_report
Goal
Produce a TiDB bug issue body from a Shiro report, then add a concise Analysis section with 1–3 likely causes.
Required inputs
- •Shiro report directory (e.g.,
reports/case_0001_...) - •
summary.json
Optional inputs
- •
case.sql,schema.sql,data.tsv,inserts.sql - •
plan_replayer.zip
Output
- •A filled issue body using
bug-report.md - •An appended Analysis section
Workflow (deterministic)
- •Read
summary.jsonand list:- •SQL (expected/actual)
- •Expected vs actual checksums/counts
- •Oracle and rewrite kind
- •TiDB version
- •Read
case.sqlandschema.sql(if present) for minimal repro steps. - •Fill
bug-report.mdfields with concrete values. - •Append Analysis:
- •1–3 likely causes
- •Evidence from SQL or plan signature differences
- •If asked, run
gh issue create; otherwise return the issue body text.
Constraints
- •Issue body must be in English.
- •Keep Analysis short and evidence-backed.
- •If
plan_replayer.zipexists, mention it in repro steps. - •For wrong-result bugs, add labels:
sig/planner,severity/major,AI-Testing,fuzz/shiro, and the affected release labels (affects-7.5,affects-8.1,affects-8.5).