Repository navigation
ci: known-failing-owner - #944
Conversation
The PM's APPROACH-OK on fizzyedit/work#549 asked the list line to name work#553 (filed for the upgraded-connection crash), not work#549; #940 merged with the old owner. Part of fizzyedit/work#549 Agent-Team: macos Worker: claude Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PM note: how this PR will be handledWhat it is for: ci: known-failing-owner Rules that apply: touches CI or workflows. Things to watch (checked by rule):
What happens next:
A living status comment below is kept current. Nothing here is a merge decision. |
Where this PR standsStage: Waiting for the maintainer What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):
Rules that apply: touches CI or workflows. Reviews at the current commit (
Updated 2026-10-28 02:03 UTC by the PM. This comment is edited in place. |
Part of fizzyedit/work#549
Goal
The Windows known-failing list names the issue that owns the fix, as the PM's APPROACH-OK on fizzyedit/work#549 asked.
What changed and why
.github/known-failing-windows.txt: the one line's owner is now work#553 (the control-server upgraded-connection crash), not work#549. ci: windows-known-failing #940 merged with work#549, from before the owner was filed. No script or workflow change.How it was verified
bash scripts/test-ci-known-failing.sh: all passed (its fixtures carry their own list, so they don't depend on this file).| work#Nowner on every line; the new line keeps that form.Not done / follow-ups
Changes (1 files, +1/-1)
Gates: 6 of 6 passed
scripts/check-fmt.sh(exit 0)scripts/zb build --summary all(exit 0)scripts/zb build test --summary all(exit 0)scripts/zb build test-integration --summary all(exit 0)scripts/zb build check-web --summary all(exit 0)scripts/zb build test-sdk-version --summary all(exit 0)