Succeeded in ATAlem TuzlakView latest
test(ai-harness): check that no sign-in deadline starts, not the process-wide timer count, so loopbackLogin's onUrl test is not flaky in CI
1807cec77f4Open on GitHubResource usage
Average and peak CPU and memory per agent, against its launch template's capacity.
By launch template
- avg
- avg → peak
- over capacity
- capacity
| Launch template | Agents | CPU (avg / peak) | Memory (avg / peak) |
|---|---|---|---|
| linux-medium-js4 vCPU 4 GB | 51 over capacity | 144.69% / 312.8% of 400% | 1.87 GB / 5.2 GB (over capacity) of 4 GB |
Agents
| Agent | CPU (avg / peak) | Memory (avg / peak) | Details |
|---|---|---|---|
| Agent 0linux-medium-js4 vCPU 4 GB | 156.73% / 293.5% | 2.14 GB / 5.2 GB (over capacity) |
See per-agent resource charts
This run didn't use Nx Agents. Enable Nx Agents to see per-agent CPU and memory for your CI runs.