Branch: refs/heads/ci-check-cross-branch Home: https://github.com/xwiki/xwiki-dev-llm Commit: 7efd1562b14fc88b5dd3726834eee140b9a22ff8 https://github.com/xwiki/xwiki-dev-llm/commit/7efd1562b14fc88b5dd3726834eee1... Author: Vincent Massol <[email protected]> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Treat one break on four branches as one break * Group incidents by repo and signature across branches: `alsoOn` names the other branches, `crossBranch` is `also-red`, and `primary` marks the one incident that carries the analysis, the comment and the paste's entry. The others are named on its line, with their own regression windows, and are analysed nowhere. * Add the `fixed-elsewhere` fix state: the same failure red on another maintained branch and green there now, with the commit that did it — a backport candidate to hand to `xwiki-backport`, never a backport this skill opens. * Require, before claiming a fix elsewhere, two consecutive failures and then two consecutive passes on that branch, the test still running there, and a commit that touches the failing file. Measured over three branches: the naive "failed, passes now" rule fires five times, all of them flickers passing; this one fires once. * Refuse the pass for a quality gate and for an unclassified break: a gate fails on aggregate metrics, and the first live run duly offered an unrelated bug fix from a third branch as its fix. * Key `flickerGroup` on the repo and the test class alone, so one flaky suite is one issue whatever branch and window each method was seen on. * Fetch a build's test report once per run, for the history walk, the flicker rating and the cross-branch check alike. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications