Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00346773467750635506351.04389843898094533922092201714674716ef00ab6d75da940b81e7a79de21dcc64cb674716ef00ab6d75da940b81e7a79de21dcc64cborigin/main674716ef00ab6d75da940b81e7a79de21dcc64cb674716ef00ab6d75da940b81e7a79de21dcc64cborigin/main674716ef00ab6d75da940b81e7a79de21dcc64cb674716ef00ab6d75da940b81e7a79de21dcc64cborigin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1714/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1714/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1714/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1714/testsfalse#17145063545561seed #17141714falsefalse17143685787SUCCESS1779424836073https://do.pingcap.net/jenkins/job/seed/1714/default-34kvvscripts/plugins/analyze-go-test-from-bazel-output.shscripts/plugins/report_job_result.shtools/deprecated/plugins/report_job_result.shtools/deprecated/plugins/report-flaky-cases.tsscripts/plugins/report-flaky-cases.ts674716ef00ab6d75da940b81e7a79de21dcc64cb1779424788000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comfeat(scripts): detect test binary panics in bazel output analyzer (#4625) ## Summary ### 1. Analyze panic crash in bazel test output - Fix section delimiter regex (`=+`) to only match start markers, not pure `====` lines — fixes broken section pairing - Fix section pairing from `(2p, 2p+1)` to `(p, p+1)` with virtual EOF marker for the last section - Add `panic:` detection: target output containing `panic:` is suffixed `.panic.log` - Add `panic:` to `indexReg` so panic lines appear in `bazel-go-test-index.log` - Add `parse_bazel_go_test_panic_cases` function that writes `crash` entries to `bazel-go-test-problem-cases.json` with: - `shard` — which shard crashed - `flaky_attempts` — how many times it crashed across retries - `cases` — ordered list of test cases in that shard - `panic` — panic message ### 2. Deprecate unused scripts - Move `report-flaky-cases.ts` → `tools/deprecated/plugins/` with symlink at original location - Move `report_job_result.sh` → `tools/deprecated/plugins/` with symlink at original location ## Testing Verified against build #3334 of `pull_integration_realcluster_test_next_gen`: - Old script produced empty `{}` JSON and broken section files - New script correctly identifies 3 panic crashes in shard 2 and reports them in JSON 2026-05-22 04:39:48 +0000674716ef00ab6d75da940b81e7a79de21dcc64cbfeat(scripts): detect test binary panics in bazel output analyzeraddtools/deprecated/plugins/report_job_result.sheditscripts/plugins/analyze-go-test-from-bazel-output.sheditscripts/plugins/report_job_result.sheditscripts/plugins/report-flaky-cases.tsaddtools/deprecated/plugins/report-flaky-cases.tsgithttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply