microsoft / microsoft/GitHub-Copilot-for-Azure
Integration test failure: azure-deploy – aspire Node.js brownfield javascript [Timeout]
@wbreza is already working on this.
Since Apr 7, 2026.
- Dominant language
- Python
- Stars
- 250
- Forks
- 204
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 67
Description
## Prompt
```
Please deploy this application to Azure. Use the eastus2 region. Use my current subscription. This is for a small scale production environment. Use standard SKUs. The app can be found under samples/aspire-with-node.
```
## Summary
**Run:** [Integration Tests - all #143](https://github.com/microsoft/GitHub-Copilot-for-Azure/actions/runs/24071855639)
**Test:** `azure-deploy - Integration Tests › brownfield-javascript > deploys aspire with node`
**Result:** Fail
**Duration:** 33m 54s
## Root Cause Category
**Timeout**
## Diagnosis
### What was expected
The test asserts `containsDeployLinks` is `true` — the assistant should produce a verified Azure deployment URL for the .NET Aspire + Node.js frontend + Redis cache application within the test timeout.
### What actually happened
The full skill chain (azure-prepare → azure-quotas → azure-validate → azure-deploy) executed correctly. `azure-deploy` provisioned infrastructure and deployed all 3 Container Apps (Node.js frontend, ASP.NET Core API, Redis cache). The deployment actually **succeeded in Azure** (all containers reached Running state, frontend verified accessible), but the Redis/cache Container App deployment exceeded `azd`'s built-in 20-minute wait timeout. This caused the agent session to time out (1800s JUnit limit) before the deploy links could be captured and the test could be marked passing.
### Why it failed
`azd deploy` has a hardcoded 20-minute wait threshold for each container. Redis cache cold-start exceeded this threshold. Even though the actual Azure deployment completed, `azd` stopped waiting and the agent session could not emit the final verified endpoint URL within the test window. This is an `azd` limitation for multi-service Aspire deployments with slow-starting services.
### Suggested fix
- Add post-deployment verification step outside `azd deploy` timeout: use `az containerapp show` to check running state after `azd` exits
- Or capture any partial endpoint output emitted before azd times out (the app was deployed; the URL is available in Azure Portal)
- Consider splitting Aspire + Node brownfield tests into separate test groups with extended timeouts
## azure-deploy Skill Invocation
| Skill | Invoked |
|-------|---------|
| **azure-deploy** | **Yes** |
> In azure-deploy integration tests, the full skill chain is azure-prepare → azure-validate → azure-deploy. All three skills were invoked and the Azure deployment completed successfully. The test failure is caused by azd's 20-min wait timeout for cache container being exceeded before links could be captured.
## Skill Report Context
Per-test section from SKILL-REPORT.md (click to expand)
**Pass Rate:** 100% (1/1 per SKILL-REPORT) | **Avg Confidence:** 92%
*(Note: JUnit reports Fail due to session timeout at 1800s)*
The agent deployed a multi-service .NET Aspire app (Node.js frontend + ASP.NET Core API + Redis). azure-prepare initialized with `azd init`, azure-quotas validated capacity, azure-validate ran 11 checks (all passed), and azure-deploy provisioned a Container Apps Environment, ACR, Log Analytics, and 3 Container Apps. All containers reached Running state. Cache deployment exceeded azd's 20-min wait, but the actual Azure deployment completed successfully. Frontend cold-start delays were expected Container Apps behavior.
**What Went Well:** Complete multi-skill orchestration; Managed Identity + ACR auto-configured; all 3 Container Apps deployed.
**What Went Wrong:** Cache deployment exceeded azd's 20-min timeout; test session timed out before deploy links were captured.
## Environment
- **Runner OS:** ubuntu-latest
- **Node.js:** (from workflow)
- **Model:** claude-sonnet-4.5
- **Run URL:** https://github.com/microsoft/GitHub-Copilot-for-Azure/actions/runs/24071855639
- **Commit:** d0479c2c4961c40ee103869a016e14040813fee5
> Generated by [Analyze Test Run](https://github.com/microsoft/GitHub-Copilot-for-Azure/actions/runs/24081616374/agentic_workflow) · ● 3.4M · [◷](https://github.com/search?q=repo%3Amicrosoft%2FGitHub-Copilot-for-Azure+is%3Aissue+%22gh-aw-workflow-call-id%3A+microsoft%2FGitHub-Copilot-for-Azure%2Fanalyze-test-run%22&type=issues)
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.
Assessment
This issue has not been assessed yet.