Repository navigation
Conversation
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. 🎉 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Agent-Team: linux Worker: claude
…ptRoot in param default, array JSON parsing - test-runner-setup.ps1: capture child pwsh output with ErrorActionPreference=Continue (5.1 turns 2>&1 stderr into a terminating error under the runner's 'Stop') - doctor.ps1: resolve default ConfigPath in the body; $PSScriptRoot is empty in param() defaults on 5.1 - test-windows-doctor.ps1: ConvertFrom-Json returns a JSON array as one object on 5.1; enumerate it explicitly Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Agent-Team: linux Worker: claude
b6719ab to
b6e5f28
Compare
|
REVIEW: changes @b6e5f28c76b73ac76735cf5328e18570bd12c535 Interim review by the PM's read-only review agents. The reviewer is Claude, the same model family as the author, so this is NOT yet a cross-kind review; builds and tests were not run by the reviewer, CI is as shown on the PR.
|
Where this PR standsStage: Author's turn 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; touches worker-machine setup or credentials. Reviews at the current commit (
1 earlier review are for older commits and will be redone. Latest fixes comment: #749 (comment) (2 findings answered) Updated 2026-10-24 09:18 UTC by the PM. This comment is edited in place. |
Machine-specific runner name, users and tasks move to a local override file (-LocalConfigPath, FIZZY_DOCTOR_LOCAL, or C:\fizzy\doctor.local.psd1). Drops the always-GREEN power plan row, bounds the zig-cache walk at 60 s, and runs the doctor tests once in the windows-doctor job. Agent-Team: linux Worker: claude Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
REVIEW: changes @bfd91edbae465a44b48025cb4cd72fab8aac30f7 Review by claude (windows team): changes requestedFinding ids are Risk: ci |
|
REVIEW: changes @bfd91edbae465a44b48025cb4cd72fab8aac30f7 Review by claude (linux team): changes requestedFinding ids are Risk: ci Checked: I read the whole diff ( Findings: Not checked: I ran nothing, so I did not execute the scripts under 5.1 or 7, and I did not run any gate or see the CI results. Win32/CIM and registry behaviour on a real Windows box, the powercfg index parsing against localized output, |
|
FIXES @bfd91edbae465a44b48025cb4cd72fab8aac30f7 |
|
REVIEW: changes @bfd91edbae465a44b48025cb4cd72fab8aac30f7 Review by codex (linux team): changes requestedFinding ids are Risk: ci |
|
REVIEW: changes @bfd91edbae465a44b48025cb4cd72fab8aac30f7 Risk: unknown; diff inaccessible |
|
REVIEW: changes @bfd91edbae465a44b48025cb4cd72fab8aac30f7 Review by agy (linux team): changes requestedFinding ids are Risk: ci |
|
PM (foxnne's decision, 2026-10-24): closed as superseded. Windows runs from the PM's own setup package, and a windows-latest job would add CI load for a machine already set up. Keeping the library lean. |
Part of fizzyedit/work#47
Changes
Gates
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)Closes fizzyedit/work#47
Rebased onto current
mainby the Linux worker. TheWindows worker doctor (PowerShell 5.1)job passed on the previous head; its output is in that job's log.Tests (Windows)hung on the unrelated fizzy-control-server-tests flake (fizzyedit/work#80, timeout in #769) and needs a rerun once those land.