Suggested test: copilot/mcp-startup-timeout-slow-server #23422

Motivation

github/gh-aw#69372 — MCP gateway health checks now honor tools.startup-timeout (retries sized to the timeout) instead of a fixed ~149s budget, which previously prevented agent startup with slow backends.

Proposed test

• Workflow file: test-copilot-mcp-startup-timeout.md
• Trigger: workflow_dispatch
• Engine: copilot
• Safe output: create-issue (or noop) to prove the agent started
• Variant: standard

Minimal test prompt sketch

Configure tools.startup-timeout: 300 and a custom MCP server whose startup is delayed (e.g. sleep 170 before listening). The agent calls one tool from it and reports the result via safe output.

New fixtures or secrets needed

A small delayed-start MCP server script/container under shared/mcp/.

Notes

Runs >150s, so it is slower than most tests. Open question: whether the delay is feasible without a custom container. Related existing tests: test-copilot-mcp, test-copilot-mcp-large-json-payload; none cover startup timeouts.

Generated by 🔍 Suggest New E2E Tests · copilot · auto · 14.6 AIC · ⌖ 0.544 AIC · ⊞ 8.7K · ◷