Repository navigation
test: split API coverage across balanced CI shards - #1908
Conversation
alandelong-oai
left a comment
There was a problem hiding this comment.
Thanks for the focused split. This owner-level merge-safety review found no blocking issues: the moved coverage and isolation are preserved, and the persistence cases retain the important cache and client transitions.
Types, formatting, and 52 shard/report tests passed. Hosted reports from the exact reviewed tree pass all three API files on Linux, macOS, and Windows; the API inventory changes only by the intended persistence split. Local API execution was limited by environment ownership checks. All current GitHub checks are successful or skipped.
dc98c63 to
f49e592
Compare
d0088ec to
4f5b34f
Compare
alandelong-oai
left a comment
There was a problem hiding this comment.
Thanks for the focused split. This owner-level merge-safety review found no blocking issues: the 154 unaffected test registrations are preserved, and the three persistence cases retain cross-client recovery, warmed-client model changes, access-program cache separation, and safety-identifier transitions.
Fresh types, formatting, and 52 shard/report tests passed. The exact reviewed tree also passed all 90 Linux validation cases, including all three persistence scenarios (27 assertions). Local API execution was limited by fixture-ownership checks. The remaining hosted matrix is still running; this approval does not imply those checks have completed.
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. |
f49e592 to
087c0c9
Compare
4f5b34f to
58bf29d
Compare
alandelong-oai
left a comment
There was a problem hiding this comment.
Thanks for the focused split. This owner-level merge-safety review found no blocking issues: the 154 unaffected registrations are preserved, and the persistence cases retain cross-client recovery, warmed-client model changes, access-program separation, and safety-identifier transitions.
Fresh SDK/plugin builds, types, formatting, and 79 focused tests passed. Local persistence and completed-bundle checks stopped at the review environment’s existing fixture-ownership guard; those checks are not claimed as passing. The current hosted matrix is still running. The exact reviewed tree also passed all 12 Windows workflow cases in hosted CI.
Summary
A Windows API shard took 817 seconds, with almost all its work in
api.test.ts, limiting what additional file-based shards could improve. Separately, a compound persistence test exceeded the existing 30-second macOS deadline. Windows retains its existing 120-second timeout.This PR splits the API tests along their existing semantic boundaries and gives the persistence/cache scenarios independent test cases. It is stacked on #1902; this parent-relative change touches only API tests and their duration metadata.
Changes
api.test.ts; move finding validation toapi-validation.test.tsand durable workflow resume toapi-workflow.test.ts. Each file owns its temporary directories and cleanup. Existing mock restoration and subprocess isolation stay intact.Testing
Current head
58bf29d270fb382e23fa0e7b24ac0f41345f0a0ais stacked on routing087c0c9607919c9d7dd9f332780f587b31c24e27, based on main8fd19efadb160153a15e0ad47d8edf32391ce463.38f4039ahas the head's source tree. All 26 SDK report/log/upload bindings were verified; all 236 shared files ran once per OS. API inventory remains 346 cases/3,542 assertions on Linux and macOS, and 343/3,499 on Windows. Every whole-suite inventory/assertion change is source-accounted, with no lost positive Linux coverage on unchanged inputs.Risk and rollout
Test organization and scheduling change; this parent-relative patch does not change package behavior. The persistence cases repeat independent setup while retaining real persistence checks. Fresh code review, scoped checks and hosted qualification of this head are complete. Land after #1902. No runtime version, timeout, retry, coverage policy, or public API changes are included.
Public disclosure review