September 2026 - notifications

[xwiki/xwiki-dev-llm]
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-stale-snapshot Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] acda60: [Misc] Stay quiet about an Environment Tests run t...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: acda60a5b3aedca5d01f11a6ffd71fdcbcedd65a https://github.com/xwiki/xwiki-dev-llm/commit/acda60a5b3aedca5d01f11a6ffd71… Author: Vincent Massol <vincent(a)massol.net> 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] Stay quiet about an Environment Tests run that used stale jars * Add `stale-snapshot` to `fixState`. The Environment Tests job builds only the test modules it was given and takes the rest of its WAR from the last snapshot deployed to Nexus, so a commit carrying a test *and* the production code that test needs is red there until the next deployment — with stack-trace line numbers read from the old file, which is exactly what a defect in the new test looks like. * Bound the snapshot by build revisions rather than by parsing a log: XWiki's CI runs Maven without transfer progress, so no build log names a resolved artifact (measured on Environment Tests `#1377`: 192 KB of step console, no download line, and the wfapi node log serves only a 10 KiB tail anyway). Two `buildRevision` calls and one compare, no Nexus call, no `consoleText`. * Take the revision of the most recent *completed* main build that had started when the environment build did — an upper bound, since a build still running has deployed nothing. Erring detects less, which is the direction a detector that buys silence must fail in. Not the last *green* one: platform's main job has been `FAILURE` on every build for days, the quality gate running after the deploy, so a green one would date the snapshot to last week. * Require one commit in that gap to touch the failing test class *and* a production file. A test change here and a production change there is an ordinary pair of commits, and reading it as the trap would silence a real breakage on a coincidence. Page objects and the docker test framework are not production: the job builds those. * Evaluate it before the forward-fix and in-flight gates. It is the only value of the three that says the test was never broken, and reporting a fix for it implies there was something to fix. * Set it only for a test failing in the environment job alone — the main job builds everything from source, so a test red there is red for real — which needs the new `failingJobs` field, `window.job` naming only the job that saw it break first. And only where the incident's first bad build is the build being examined: one that survived the next run met jars that had caught up. Verified against xwiki-platform/master, where Environment Tests `#1377` started 13 minutes after a commit that pushed `VersionIT` and `XWikiHibernateVersioningStore` together, and the incident that S1 reported as "possibly fixed already" now reads as the trap it is. The two blocknote flickers pass every guard and stay `null`, no commit in the gap naming them. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> Commit: b4d19df9ddb9a9e73e475b9bd1b1cb5f718958c8 https://github.com/xwiki/xwiki-dev-llm/commit/b4d19df9ddb9a9e73e475b9bd1b1c… Author: Vincent Massol <vincent(a)massol.net> 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: ----------- Merge pull request #153 from xwiki/ci-check-stale-snapshot [Misc] Stay quiet about an Environment Tests run that used stale jars Compare: https://github.com/xwiki/xwiki-dev-llm/compare/e26dfc84128b...b4d19df9ddb9 To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] acda60: [Misc] Stay quiet about an Environment Tests run t...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-stale-snapshot Home: https://github.com/xwiki/xwiki-dev-llm Commit: acda60a5b3aedca5d01f11a6ffd71fdcbcedd65a https://github.com/xwiki/xwiki-dev-llm/commit/acda60a5b3aedca5d01f11a6ffd71… Author: Vincent Massol <vincent(a)massol.net> 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] Stay quiet about an Environment Tests run that used stale jars * Add `stale-snapshot` to `fixState`. The Environment Tests job builds only the test modules it was given and takes the rest of its WAR from the last snapshot deployed to Nexus, so a commit carrying a test *and* the production code that test needs is red there until the next deployment — with stack-trace line numbers read from the old file, which is exactly what a defect in the new test looks like. * Bound the snapshot by build revisions rather than by parsing a log: XWiki's CI runs Maven without transfer progress, so no build log names a resolved artifact (measured on Environment Tests `#1377`: 192 KB of step console, no download line, and the wfapi node log serves only a 10 KiB tail anyway). Two `buildRevision` calls and one compare, no Nexus call, no `consoleText`. * Take the revision of the most recent *completed* main build that had started when the environment build did — an upper bound, since a build still running has deployed nothing. Erring detects less, which is the direction a detector that buys silence must fail in. Not the last *green* one: platform's main job has been `FAILURE` on every build for days, the quality gate running after the deploy, so a green one would date the snapshot to last week. * Require one commit in that gap to touch the failing test class *and* a production file. A test change here and a production change there is an ordinary pair of commits, and reading it as the trap would silence a real breakage on a coincidence. Page objects and the docker test framework are not production: the job builds those. * Evaluate it before the forward-fix and in-flight gates. It is the only value of the three that says the test was never broken, and reporting a fix for it implies there was something to fix. * Set it only for a test failing in the environment job alone — the main job builds everything from source, so a test red there is red for real — which needs the new `failingJobs` field, `window.job` naming only the job that saw it break first. And only where the incident's first bad build is the build being examined: one that survived the next run met jars that had caught up. Verified against xwiki-platform/master, where Environment Tests `#1377` started 13 minutes after a commit that pushed `VersionIT` and `XWikiHibernateVersioningStore` together, and the incident that S1 reported as "possibly fixed already" now reads as the trap it is. The two blocknote flickers pass every guard and stay `null`, no commit in the gap naming them. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm]
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/tags/v1.12.4 Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] e26dfc: [Misc] Release 1.12.4
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: e26dfc84128bff59190bfed6826523ced339f67e https://github.com/xwiki/xwiki-dev-llm/commit/e26dfc84128bff59190bfed682652… Author: github-actions[bot] <41898282+github-actions[bot](a)users.noreply.github.com> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M .claude-plugin/marketplace.json M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json Log Message: ----------- [Misc] Release 1.12.4 * content edits only (no capability added or removed) To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm]
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-in-flight-fix Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] e36d6b: [Misc] Stay quiet about a CI incident an open PR a...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: e36d6bec86101d75d794fbd0b931f2e42c91af6b https://github.com/xwiki/xwiki-dev-llm/commit/e36d6bec86101d75d794fbd0b931f… Author: Vincent Massol <vincent(a)massol.net> 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] Stay quiet about a CI incident an open PR already answers * Add `fix-in-flight` to `fixState`: an open PR whose title or body names the failing test class, or the JIRA key the incident is tracked as, buys the same silence a landed-but-unbuilt commit does — no deep slot, no commit comment, one line in the paste. Root-causing a test somebody is visibly working on is arguing with the room. * Run it only where the branch itself holds nothing: a landed commit will be judged by the next build, a PR is somebody's intent, and the stronger evidence is what the reader needs. Inherits S1's coverage rule whole — a PR answering one failing class of two leaves the incident live, with its blame and its comment. * Read the open PRs once per repo per run, never per incident: the plain `pulls` list newest-updated first, stopping at the first PR outside a 14-day window, three pages at most. That is 1-2 requests for xwiki-platform's ~230 open PRs, on the core quota rather than the search API's own budget. * Require the PR's base branch to be the incident's branch. A master PR cannot fix `stable-17.10.x`, and silencing that branch on it would hide a break nobody is working on. * Let a JIRA key answer for the whole incident only when the incident is a single test class — the key is the flicker issue of its first test and says nothing about classes that merely broke in the same build. * Give `fixState` a `where` clause and a per-kind headline, so the four places that render it stop spelling out one kind's story and the next value is a row in a table rather than a branch in each of them. * Word it *may be in flight*, never *fixed*: the PR may be a rewrite that touches the test, and it may never merge. What settles it is the merge, not this run. Verified against xwiki-platform/master: the live sweep is unchanged (the one answered incident is still `fix-unbuilt`, and no open PR names the other three), and a probe with the forward pass short-circuited matches `#6456` and correctly reports it as partial. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> Commit: 802a3df5870cf42e6418759e0c3313dfbe34be06 https://github.com/xwiki/xwiki-dev-llm/commit/802a3df5870cf42e6418759e0c331… Author: Vincent Massol <vincent(a)massol.net> 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: ----------- Merge pull request #152 from xwiki/ci-check-in-flight-fix [Misc] Stay quiet about a CI incident an open PR already answers Compare: https://github.com/xwiki/xwiki-dev-llm/compare/3014ce3944f5...802a3df5870c To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] e36d6b: [Misc] Stay quiet about a CI incident an open PR a...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-in-flight-fix Home: https://github.com/xwiki/xwiki-dev-llm Commit: e36d6bec86101d75d794fbd0b931f2e42c91af6b https://github.com/xwiki/xwiki-dev-llm/commit/e36d6bec86101d75d794fbd0b931f… Author: Vincent Massol <vincent(a)massol.net> 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] Stay quiet about a CI incident an open PR already answers * Add `fix-in-flight` to `fixState`: an open PR whose title or body names the failing test class, or the JIRA key the incident is tracked as, buys the same silence a landed-but-unbuilt commit does — no deep slot, no commit comment, one line in the paste. Root-causing a test somebody is visibly working on is arguing with the room. * Run it only where the branch itself holds nothing: a landed commit will be judged by the next build, a PR is somebody's intent, and the stronger evidence is what the reader needs. Inherits S1's coverage rule whole — a PR answering one failing class of two leaves the incident live, with its blame and its comment. * Read the open PRs once per repo per run, never per incident: the plain `pulls` list newest-updated first, stopping at the first PR outside a 14-day window, three pages at most. That is 1-2 requests for xwiki-platform's ~230 open PRs, on the core quota rather than the search API's own budget. * Require the PR's base branch to be the incident's branch. A master PR cannot fix `stable-17.10.x`, and silencing that branch on it would hide a break nobody is working on. * Let a JIRA key answer for the whole incident only when the incident is a single test class — the key is the flicker issue of its first test and says nothing about classes that merely broke in the same build. * Give `fixState` a `where` clause and a per-kind headline, so the four places that render it stop spelling out one kind's story and the next value is a row in a table rather than a branch in each of them. * Word it *may be in flight*, never *fixed*: the PR may be a rewrite that touches the test, and it may never merge. What settles it is the merge, not this run. Verified against xwiki-platform/master: the live sweep is unchanged (the one answered incident is still `fix-unbuilt`, and no open PR names the other three), and a probe with the forward pass short-circuited matches `#6456` and correctly reports it as partial. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm]
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/tags/v1.12.3 Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 3014ce: [Misc] Release 1.12.3
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: 3014ce3944f5041a6be3e9f6b630605492955d1f https://github.com/xwiki/xwiki-dev-llm/commit/3014ce3944f5041a6be3e9f6b6306… Author: github-actions[bot] <41898282+github-actions[bot](a)users.noreply.github.com> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M .claude-plugin/marketplace.json M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json Log Message: ----------- [Misc] Release 1.12.3 * content edits only (no capability added or removed) To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0