ci: route nightly tick controls through fleet picker

Closed
TE
2d ago
+17-2

HOLD: main-source live admission repair is incomplete; the current head must not land.

The nightly-next tick request job was pinned to blacksmith-2vcpu-ubuntu-2404; run 41286823037 remained queued while that pool admitted nothing. The tick and feed-watch control jobs now use the live CI_CONTROL_RUNNER picker result first and fall back to hosted Ubuntu under the declared light Linux exception. The CI routing test rejects the old Blacksmith pin across all nightly-next control workflows.

Validation:

  • PYTHONPATH=tests python3 -m unittest tests.test_ci_nightly_off_blacksmith (11 passed, 1 skipped)
  • PyYAML parse of both changed workflows
  • git diff --check

agent-identity footer --repo manaflow-ai/cmux
agent session


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.


Summary by cubic

The nightly-next tick request job stayed queued because it was pinned to blacksmith-2vcpu-ubuntu-2404, a pool that admitted nothing (run 41286823037). The tick and feed-watch control jobs now use the live CI_CONTROL_RUNNER fleet-picker result first and fall back to hosted Ubuntu as the light-linux exception.

Bug Fixes

  • The CI routing test rejects the old Blacksmith pin across all nightly-next control workflows.