---
id: "bug-1857"
status: "fixed"
status_updated: "2026-09-24"
status_note: "3cc2f6e3"
component: "config"
severity: "unknown"
timestamp: "2026-09-24T13:02:14Z"
last_seen: "2026-09-24T13:02:14Z"
occurrences: 1
files: [".claude/skills/xce-test-multihost/run-multihost-verify.sh", "src/tools/deploy-ha.sh", "src/configs/limits.yaml"]
tags: ["test-fixture", "scheduler", "limits", "multihost"]
related: []
fix_commits: ["3cc2f6e3"]
legacy: true
gitea_issue: 276
gitea_synced_status: "fixed"
---

# bug-1857: xce-test-multihost FAIL: job never reached RUN within 30s (last observed state: PEND)…

## Description
xce-test-multihost FAIL: job never reached RUN within 30s (last observed state: PEND); scheduler.log: 'unsatisfy_ unmet resource 33 (limit=limit1) shortfall 30.000000'

## Environment
_Not recorded (migrated from buglog.json)._

## Reproduction
_Not recorded (migrated from buglog.json)._

## Root cause
run-multihost-verify.sh deploys with the repo's default src/configs/limits.yaml, whose limit1 caps all users except rshen at a shared 3 slots. xce_test submits as root, so the 33-task job is capped. The fixture passed 2026-09-06 only because global limits did not yet count a job's full task total; the bug-1790 fix (9caf1424, 2026-09-08) correctly started doing so, leaving the fixture stale. Allocator itself is fine: passes with limit1 raised to 100.

## Fix
UPDATE (2026-09-24): Fix (uncommitted): deploy-ha.sh gains optional XCE_DEPLOY_CONFIG_DIR (default unchanged: src/configs); run-multihost-verify.sh copies src/configs into $TOP/configs, replaces limits.yaml with 'limits: []', and deploys with that override. Verified 2026-09-24: multihost e2e PASS (plain 33-task job + array element both split across 2 hosts, DONE), 0 limit1 rejections; default deploy path still builds from repo configs; bad override fails with 'config dir not found'.

## Verification
_Not recorded (migrated from buglog.json)._

## References
- Gitea: #276