ECS runner fleet is stale: the qwen update failed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28k
- Forks
- 3.1k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 714
Description
Update ECS Runner Qwen failed, so at least one ECS pool is still running an older qwen than the release it was asked to install.
- Target version:
0.23.3 - Pools left stale: ecs-update-hk-1, ecs-update-hk-2
- Run: https://github.com/QwenLM/qwen-code/actions/runs/34571240062
Nothing else surfaces this. The review and triage workflows install qwen only when command -v qwen finds nothing, which on a self-hosted runner is never, so a stale pool keeps reviewing PRs on the old CLI until someone reads a version string.
To repair: re-run Update ECS Runner Qwen through workflow_dispatch (an empty version means latest), then read the Verify version step of every pool.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Update ECS Runner Qwen workflow and run 34571240062, using workflow_dispatch with an empty version to request the latest qwen. Read the Verify version step for ecs-update-hk-1 and ecs-update-hk-2; done means both pools report version 0.23.3 or newer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 82/100