Repository navigation
test: check native Python reports in the Python matrix - #1950
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. |
alandelong-oai
left a comment
There was a problem hiding this comment.
Thanks! Owner-level merge-safety review is clean. Moving the fixtures into the Python matrix preserves the native report gate and removes the repeated SDK-launched interpreters. The Python cases, SDK skeleton tests, direct CLI checks, and workflow linting passed; the new fixture step also passed on all three hosted operating systems.
eaed09a to
21ec216
Compare
alandelong-oai
left a comment
There was a problem hiding this comment.
Thanks! Owner-level merge-safety review of 21ec216 is clean. The Python matrix now exercises the report gate without repeated SDK-launched interpreters, while the native jobs still require the designated nonempty report with no skipped cases. All five Python cases, five direct CLI cases, 19 SDK skeleton tests, types, formatting and workflow lint passed. The exact-head report-fixture step also passed on Linux, macOS and Windows CI. Full native/SDK suites were not rerun locally.
Summary
Run the native Python report checks in the Python matrix. A Windows SDK shard reached its ten-second child deadline while starting the first of five interpreters. The expected missing-file failure appeared as a null exit status. This change is stacked on #1931. Windows job
Changes
Testing
Risk and rollout
This affects repository CI. The native gate still reads
reports/python.xmland fails on missing, malformed, empty, or skipped coverage. Reverting this commit restores the original workflow and SDK fixture.Public disclosure review