Repository navigation
test: split Windows CI and test the installed package - #1102
Conversation
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. |
e29a658 to
f2c3eed
Compare
|
@codex review |
|
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". |
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The CI and package-verification changes are coherent, targeted, and directly covered by tests.
Review effort: Balanced
Findings: None
What changed in this PR
Improves CI reliability and validates installed npm package contents more thoroughly.
Changes:
- Shards Windows isolated tests, updates Bun, and adjusts timeout/report handling.
- Moves launcher verification into installed-package smoke tests.
- Scans package paths, metadata, plaintext, and expanded Brotli assets for internal references.
| File | Description |
|---|---|
.github/workflows/node-ci.yml |
Lets test steps use job-level deadlines. |
.github/workflows/test-quality.yml |
Updates Bun, Windows sharding, timeouts, and report comparison. |
sdk/typescript/scripts/check-package.mjs |
Integrates package-content validation. |
sdk/typescript/scripts/package-public-content.mjs |
Validates public paths, metadata, and compressed assets. |
sdk/typescript/scripts/smoke-package.mjs |
Tests the installed CLI launcher. |
sdk/typescript/tests-ts/cli-launcher.test.ts |
Removes duplicated source-build launcher coverage. |
sdk/typescript/tests-ts/package-public-content.test.ts |
Covers package-content validation behavior. |
sdk/typescript/tests-ts/test-reports.test.ts |
Accounts for sharded report patterns. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
soyeon-oai
left a comment
There was a problem hiding this comment.
Reviewed current ACL EOF/chunk handling and its callers, package-content validation, launcher smoke coverage, and Windows sharding/inventory checks. No actionable findings. The earlier Bun regression in discussion_r4146928685 is addressed by current test changes: the Windows baseline log shows Bun 1.4.2, both cited terminal tests and both ACL EOF cases passing (3234 pass, 0 fail): https://github.com/openai/codex-security/actions/runs/36877426698/job/110423108643 . Hosted CI inspected; no independent execution.
alandelong-oai
left a comment
There was a problem hiding this comment.
The Windows ACL reader now drains buffered descriptors through EOF, while package checks validate decoded contents and the installed launcher. Three independent high-reasoning reviews plus source verification found no new actionable findings.
Validation at 75d6f5cb78812d7967ae03d641c4f32922274049: 110 package-content, publication, dashboard, and report tests passed under Bun 1.4.2; three focused ACL streaming/failure tests passed. The earlier terminal-test issue in discussion_r4146928685 is addressed by the current changes. Full installed-package and native Windows execution were not run locally.
|
@codex review |
|
Codex Review: Didn't find any major issues. Another round soon, please! 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". |
|
@codex review |
|
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". |
alandelong-oai
left a comment
There was a problem hiding this comment.
Re-reviewed the updated PR at d15e40d against base 794e046 with three fresh independent high-reasoning passes and root verification. No actionable findings remain in this diff.
Validation: 287 focused tests passed (22 platform-specific skips), SDK/MCP typechecks and formatting passed, clean plugin/SDK builds passed, and the 528-entry installed package passed CLI, SDK lifecycle, credential-locking, MCP initialization, and nested-worker checks. Checks were rerun after refreshing dependencies to this commit's lockfiles. Local execution was on macOS; native Windows CI is still running. This approval does not imply the rest of the stack is ready to merge.
Part 1 of 46. Next: #1103 · Stack index
Summary
Split the Windows isolated test run into seven jobs and move launcher checks into the installed-package smoke test. Also fix a Windows credential ACL reader race that could lose buffered output when its subprocess exited.
Changes
Testing
Final-head node-ci passed at
d15e40d: 66 jobs passed and one was skipped. The first Ubuntu isolated-test attempt timed out; its diagnostic rerun passed on unchanged code with 3,369 tests, 51 skips, and no failures. The dependent inventory comparison passed too. Post-merge node-ci passed at688e2ae(45 jobs passed, one skipped).18fcffc: seeded (12345) and randomized (3621653093) runs each passed 3,367 tests with 51 platform-specific skips and no failures.d15e40d, 751 focused tests passed with ten platform-specific skips, covering model defaults, API and CLI behavior, dedupe and comparison, and terminal rendering. The Deep Scan worker boundary suite also passed.Risk and rollout
CI and package validation change immediately. The ACL reader keeps the existing permission checks while draining complete and partial stdout lines through EOF. No public command or option changes.
Review the stack
This stack combines the Deep Scan work from #939 and #1095. Each Deep Scan pass becomes an ordinary Standard scan; a separate merge step combines the saved findings and evidence. It includes the approved review fixes and simplifications.
Parts 1–19 extract shared scan behavior and introduce child tracking, merging and recovery. Parts 20–38 finish settings, packaging and saved-result handling. Part 39 switches the SDK, and part 40 switches the plugin. Parts 41–46 remove the retired implementation.
Review in order against each PR’s selected base. Part 1 targets
main; every later PR targets the preceding branch. The individual descriptions distinguish changes active at that step from helpers connected later.Public disclosure review