perf(test): measure the Windows column of the wall-clock baseline and the gate, affected-run and corpus targets

Parent: #3716 (slice 2 of 3). Blocked by #10200 (slice 1).
Runs in: HOST. Needs a healthy Windows 11 Git Bash host; the lane runs on Linux; the host runner works it.

Problem

#3716 criteria 1 to 4 are Windows measurements: the Windows column of the baseline table, no gate script over 60 s, scripts/affected-tests.sh --run on a typical 50-file diff under 2 minutes, and the full scripts/run-plugin-tests.sh corpus under 10 minutes with the number recorded. No current Windows number exists; the last ones are from 2026-09-04 to 2026-09-08 (#3716 comment), before many optimizations.

Fix

On a Windows host that does not carry the #3715 process-creation condition (or record that it does), at a stated origin/main commit:

Run the full corpus with slice 1's timing option and fill the Windows column of docs/test-wall-clock-baseline.md, with the total.
Time each gate script slice 1 lists in its typical single-diff invocation.
Run scripts/affected-tests.sh --run over a real merged 50-file diff (name the commit range) and record the time.
Open one PR with the doc update. In the PR body list every gate script over 60 s, and say whether criteria 3 and 4 are met.

Done when

docs/test-wall-clock-baseline.md has a filled Windows column, the host's OS build, Git Bash version and the commit measured
The doc records the full-corpus Windows total and the 50-file affected-tests.sh --run time with its commit range
The PR body lists each gate script over 60 s on Windows, or states there is none
A comment on test-perf: diagnose and cut the wall clock of the local test and gate corpus, especially on Windows Git Bash #3716 states which of criteria 2, 3 and 4 are met, so per-offender slices can be filed for the rest
ci-status is green on the PR head

Split by the backlog HITL session (2026-10-25, owner rule Q93: split large work before a run picks it up). This was generated by AI.

Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.

Size: Small
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: #10200

Understood: on a Windows 11 Git Bash host, measure the full test corpus, the gate scripts, and a 50-file affected-tests.sh --run. Then fill the Windows column of docs/test-wall-clock-baseline.md and open one PR. The work needs the timing option and baseline doc from #10200 first. The Windows measurements need a host run, which an unattended Linux lane can't do. I found no duplicates among the open issues.

_{Automated triage, applied by the lanes App.}

Not admitted to the issue lane yet: blocker #10200 is not closed by a listed human or a merge.

No description provided.

The work-resolve-issue lane stopped on this issue (host-only): the run reports the work needs a host run the lane cannot make.
It added host-run and removed agent-ready: an agent run on a host builds it, and it waits on no decision from a person.

In the run's words:

host-only: every done-when item needs wall-clock timings taken on a Windows 11 Git Bash host (full plugin test corpus, each gate script, and scripts/affected-tests.sh --run over a 50-file diff), plus the host's OS build and Git Bash version. The issue says 'Runs in: HOST', and this CI lane runs on Linux, so it cannot produce those numbers. Writing Linux timings or guessed values into the Windows column of docs/test-wall-clock-baseline.md would not meet the issue.

What the run says it did not do:

Fill the Windows column, full-corpus total, 50-file affected-tests.sh --run time and host details: needs a Windows Git Bash host
Comment on ＃3716 saying which of criteria 2-4 are met: depends on the Windows measurements
Repository checks (check-changelog-fragments, check-changed-skills, check-affected) not run: the run stopped before any change, and the working tree is clean

Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41464998351

To hand it back to the lane, remove host-run and add agent-ready again.

Navigation Menu

Repository navigation

perf(test): measure the Windows column of the wall-clock baseline and the gate, affected-run and corpus targets #10241

Problem

Fix

Done when

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

perf(test): measure the Windows column of the wall-clock baseline and the gate, affected-run and corpus targets #10241

Description

Problem

Fix

Done when

Activity

github-actions commented on Oct 26, 2026

melodic-automation-lanes commented on Oct 26, 2026

github-actions commented on Nov 2, 2026

github-actions commented on Nov 2, 2026

melodic-automation-lanes commented on Nov 2, 2026

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions