fix(ci): wait for Telegram credential capacity#105535
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 77f47e7576
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
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".
| OPENCLAW_QA_CONVEX_SITE_URL: ${{ secrets.OPENCLAW_QA_CONVEX_SITE_URL }} | ||
| OPENCLAW_QA_CREDENTIAL_ACQUIRE_TIMEOUT_MS: "60000" | ||
| # Keep the CLI lease wait aligned with the validated workflow contract above. | ||
| OPENCLAW_QA_CREDENTIAL_ACQUIRE_TIMEOUT_MS: "600000" |
There was a problem hiding this comment.
When this workflow timeout is raised to 600000, test/scripts/package-acceptance-workflow.test.ts:2535 still lists the release Telegram QA workflow's expected acquire timeout as "60000"; whenever that test runs, it parses this step and the assertion at test/scripts/package-acceptance-workflow.test.ts:2549 now compares "600000" to "60000", so the package-acceptance workflow test lane fails until the shared contract test is updated too.
Useful? React with 👍 / 👎.
|
Merged via squash.
|
* fix(ci): wait for Telegram credential capacity * test(ci): align Telegram credential wait contract
1 participant
What Problem This Solves
Release trains can overlap on the bounded Telegram QA credential pool. A one-minute acquisition deadline turns ordinary pool contention into a release-check failure even though the job and lease budgets are much longer.
Why This Change Was Made
Raise both workflow-owned acquisition deadlines from one minute to ten minutes. The wait remains bounded by the 60-minute job timeout and two-hour lease TTL.
User Impact
No runtime behavior change. Telegram live release checks tolerate overlapping lanes instead of failing during short-lived credential contention.
Evidence
test/scripts/openclaw-release-telegram-qa-workflow.test.ts: 20/20 passed on fresh Blacksmith Testboxtbx_01kxbkp3dggvjesp0a9sts8zdroxfmt --check: both touched files cleangit diff --check: clean