Repository navigation
ci: tier compatibility tests and require nightly wheel acceptance - #255
Conversation
|
Follow-up tier integration is now published at
Future costly cases add their required node identities alongside their actual files. No absent future tests are required by this commit. GitHub manual/nightly execution is still unverified; local acceptance does not replace that evidence. |
|
Validation update for exact head Python 3.13: 2,652 passed, 14 skipped, 1 nightly deselected, branch coverage 93.18%; independent coverage floors, wheel build/source audit, clean-wheel acceptance, and required Chromium job passed. The 14 regular-suite skips are the 12 browser cases covered by the separate required Chromium job and 2 unsupported slice-leak combinations. Frozen local tree also passed the full PR coverage run (2,652/14/1; 93.18%) and the real required nightly wheel runner (1 passed, no skips). Remote manual/nightly execution remains unverified: the available connector has no dispatch action, local gh is unauthenticated, and the assistant-cloud GitHub browser is signed out. No assertion is made that the nightly workflow has run remotely. Draft state retained. |
Local combined verification of #255–#263A separate local integration branch combined the nine independently reviewed changes, including the bilingual documentation correction now on #260. No GitHub merge was performed. Frozen local source
Environment limits remain explicit: local Python 3.13 lacked ensurepip for the fresh-venv gate, so that unchanged wheel gate was rerun successfully under 3.12; an initial inside-checkout temporary directory was rejected by the isolation guard and corrected without source changes. An extra local Chromium attempt was blocked before page execution by the environment's socket permission restriction. Individual hosted PR browser jobs passed independently. Failed setup logs were retained, not counted as successful tests. Remote nightly was not dispatched. Windows #257's CI-only two-way partition correction is still being verified and is not included in this frozen source identity. Draft PRs and issues remain open. |
检视结论:approve对照 #248 CI 分层:3.10–3.12 建议作为合入地基先合。本评论不 approve/merge。 |
codeasier
left a comment
There was a problem hiding this comment.
LGTM,已转为正式 PR。GitHub 不允许作者账号提交 APPROVE,以本评论 + 此前检视评论作为通过记录。建议作为合入地基先合。
Summary
-m "not slow"; keep the existing full slow suite, branch coverage, and unchanged 90/90/88/84 coverage floors on Python 3.13.slow, leaving their small semantic cases in every Python lane.Refs #248. This is the CI foundation, not completion of the umbrella issue or #250. The existing installed-wheel test still uses
pip --targetand 500,002 events; clean venv isolation, two full default-sized shards and broader public CLI coverage belong to the follow-on acceptance PRs.Validation
git diff --checkpassed.c5e2d0950208e79d6704557dcb3b4808f30aba2f. The required installed-wheel runner passed exactly one test with matching checkout and wheel evidence.Follow-on tier integration
New high-cost #250/#252 acceptance cases should be explicitly marked
nightlyand selected only by the nightly/manual tier in a follow-on integration change. Existingslowcoverage must remain in the Python 3.13 PR lane. No live model, real user session, upstream GUI or local Mac was used.