mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-11-07 06:19:43 -10:00
易良
29ad82d6a3
* ci: route the merge queue's Linux jobs onto ECS The merge queue runs in the base-repo context but classify_pr was PR-only, so its ubuntu_runner output was empty in the queue and the Ubuntu Test + Integration jobs fell back to the shared hosted pool — piling onto the scarce hosted Linux runners exactly when the queue is busiest. Run classify_pr on merge_group too and route both the Ubuntu gate and Integration onto the same in-repo ECS pool as PRs; the MAINTAINER_ECS_RUNNER_DISABLED kill-switch and the hosted fallback are intact, and fork PRs are unaffected. Also extend the checkout-verification guard to the merge queue: now that the queue's Ubuntu checkout runs on ECS behind the squid egress proxy, a stale-ref checkout could silently test the wrong tree, and a wrong-tree pass in the queue would merge bad code. One sub-second merge-base check. Routing approach carried forward from #5853 by @wenshao (closed); this adds the merge-queue checkout guard on top. * ci: fix verify-step wiring test and guard integration_cli on ECS The merge-queue ECS routing renamed the test job's checkout guard to "Verify checkout includes expected head commit", but no-ak-integration-ci.test.js still asserted the old "Verify PR checkout includes head commit" name, failing the wiring test. Update the assertion. integration_cli now also routes to ECS (via classify_pr on merge_group) yet lacked the protections the Ubuntu gate has. Mirror them: fetch-depth 1 (nothing walks history; a full clone is the heaviest transfer on the ECS runner) and the same stale-checkout guard, keyed on merge_group.head_sha. * ci: mirror the Node 22 version probe into integration_cli The self-hosted Node step claimed to mirror the Ubuntu gate but omitted the major-version probe, so a non-22 Node on the ECS runner would run integration tests with no log signal. Add the same warning-only check.