Branch: refs/heads/claude/wonderful-curie-81zwvt Home: https://github.com/xwiki/xwiki-dev-llm Commit: 7b58a6dff6bf71c6b371a9d5b2e41652a6508f00 https://github.com/xwiki/xwiki-dev-llm/commit/7b58a6dff6bf71c6b371a9d5b2e416... Author: Claude <[email protected]> Date: 2026-10-08 (Thu, 08 Oct 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Let the CI sweep blame a test broken for more than eight builds, and open two more kinds of fix PR In 16 daily runs the routine opened no fix PR: not one failure was a Tier A fix, and the two that a bot could have helped with fell outside the tiers or lost their culprit. * Blame: a deep test breakage with no green build in --history is walked back over every build Jenkins retains (--blame-history, default 25). BrowserPDFPrinterTest was red from build `8989` to `9004` with its last green at `8988`, so it came back "ambiguous" and its author was never told; with the deeper window `de77ad26` is the only commit touching the package. * Tier A additive: a failing coverage check is fixed by adding unit tests through xwiki-increase-test-coverage, never by lowering the ratio (the netflux-api case, fixed by hand six hours after the run). * Tier B follows-the-culprit: a draft PR, assigned to the culprit author and phrased as a question, when a unit test still expects the value the culprit's own diff changed. Unit tests only, certain or likely blame only, never for a flicker. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_017rkD3D3UwZ8H9K1yy4Yxwj To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications