test(ci): allow slower Windows Hub cold starts - #7273
Conversation
|
Hi @rayrayraykk, this is your 263rd Pull Request. 🙌 Join Developer CommunityThanks so much for your contribution! We'd love to invite you to join the official QwenPaw developer group! You can find the Discord and DingTalk group links under the "Developer Community" section on our docs page: We truly appreciate your enthusiasm—and look forward to your future contributions! 😊 We'll review your PR soon. |
There was a problem hiding this comment.
Pull request overview
Adjusts the packaged Hub Local runtime E2E test to better tolerate slower Hub cold starts on hosted Windows runners by expanding the Hub readiness wait budget, while still failing if the Hub process exits or never becomes ready.
Changes:
- Introduces a named constant for Hub readiness timeout.
- Increases Hub readiness deadline from 60s to 120s by using the new constant.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Description
Increase the Hub readiness budget in the packaged Local runtime E2E test from 60 to 120 seconds.
The failing Windows job completed all 7,962 unit tests, then timed out while waiting for the packaged Hub process to bind. The child process remained alive and its log stopped after CLI startup, so the final WinError 10061 was the last readiness probe rather than a port-binding failure. Historical successful Windows runs of the same E2E took about 110 and 132 seconds end to end, which shows that the previous 60-second Hub cold-start budget was too tight on hosted Windows runners.
This keeps the real Windows E2E enabled and preserves hard failures when the Hub process exits or does not become ready within the expanded budget. It does not xfail or suppress product errors.
Related Issue: Relates to #7268
Security Considerations: None. This changes only an E2E readiness deadline.
Type of Change
Component(s) Affected
Checklist
pre-commit run --all-fileslocally and it passespytestor as relevant) and they passFor Channel Changes (DingTalk, Lark, QQ, Console, etc.)
./scripts/check-channels.sh(or./scripts/check-channels.sh --changed) and it passestests/contract/channels/test_<channel>_contract.py(REQUIRED)create_instance()with proper channel initializationtests/contract/channels/__init__.py)tests/unit/channels/test_<channel>.pyfor complex internal logicTesting
Run the packaged Hub Local runtime E2E on the Python 3.11 Windows matrix entry. The test must still start the Hub, register a user, start an isolated Local runtime, proxy its health endpoint, and stop the runtime successfully.
Evidence
Failing Windows job: https://github.com/agentscope-ai/QwenPaw/actions/runs/32817133090/job/97711270532
Historical successful Windows E2E: https://github.com/agentscope-ai/QwenPaw/actions/runs/32465714880/job/96721841254
Additional Notes
This is intentionally separate from #7268 because the failure is pre-existing Windows CI timing behavior and is unrelated to the heartbeat source-timeout change.