Skip to content

stage-qa reports 'not provisioned': qa-cli cannot find the stage bot after the QA Telegram login move to the server #958

Open

Description

@alex-mextner

What

On 2026-11-02 the stage-qa check of #942 failed twice (run https://github.com/alex-mextner/HyperCalendarBot/actions/runs/41424818802, attempts 1 and 2, the second at 11:26 UTC) with STAGE_SMOKE_UNAVAILABLE ConnectionError: qa send failed: timed out after 10s waiting for search result for the stage bot, then STAGE_QA_RESULT status=not-provisioned cases=0. The PR's own checks (test, type-bans, lint-check, leftover-grep and the others) pass on the exact head d7a6fb8. It coincided with the owner-authorized move of the shared QA Telegram login to the build server announced on 2026-11-02 around 10:00 UTC. Next action: on the browser host run qa telegram status and search for the stage bot username as the forced command does, fix the login/session or the search, then re-run the Stage QA workflow for the PR. This is infrastructure, not a verdict on the PR.

Why (motivation)

gh ship refuses a PR without a green stage-qa for its exact head, so every PR is blocked while the QA login cannot find the stage bot.

User impact

No pull request can be shipped while stage-qa cannot run; the fix for the queued-message confirmation (PR 942) waits on it.

Cost of inaction

All PR shipping stays blocked.

Acceptance criteria

  • qa telegram status prints logged-in on the browser host and a search for the stage bot username returns it
  • Re-running the Stage QA workflow for the head of PR 942 posts a stage-qa status of success or a genuine case failure, not not-provisioned

Screenshots

(none)

Deploy

Deployed: no

Links

  • (none)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions