Motivation
github/gh-aw#49448 — fixed sandbox.agent.memory frontmatter field being silently dropped (never reached --memory-limit in compiled AWF invocation). Also added compile-time format validation via validateAgentMemoryLimit.
Proposed test
- Workflow file:
test-copilot-sandbox-agent-memory.md
- Trigger:
workflow_dispatch
- Engine: copilot
- Safe output:
create-issue
- Variant: standard
Minimal test prompt sketch
Set sandbox.agent.memory: 2g in frontmatter, then have the agent create an issue confirming it ran (a smoke test that the workflow compiles and runs successfully with the memory limit applied — similar in spirit to test-copilot-restore-memory-custom-job.md but for the sandbox memory limit rather than cache-memory).
New fixtures or secrets needed
None.
Notes
Not to be confused with cache-memory/restore-memory (already covered by test-copilot-restore-memory-custom-job.md). This targets the separate sandbox.agent.memory field that maps to --memory-limit. Primary value is confirming the lock file actually contains --memory-limit 2g and that the run doesn't fail (e.g. OOM/exit 137) — could be checked via a follow-up grep on the generated .lock.yml rather than requiring live verification.
Generated by 🔍 Suggest New E2E Tests · auto · 30.2 AIC · ⌖ 8.86 AIC · ⊞ 8.3K · ◷
Motivation
github/gh-aw#49448 — fixed
sandbox.agent.memoryfrontmatter field being silently dropped (never reached--memory-limitin compiled AWF invocation). Also added compile-time format validation viavalidateAgentMemoryLimit.Proposed test
test-copilot-sandbox-agent-memory.mdworkflow_dispatchcreate-issueMinimal test prompt sketch
Set
sandbox.agent.memory: 2gin frontmatter, then have the agent create an issue confirming it ran (a smoke test that the workflow compiles and runs successfully with the memory limit applied — similar in spirit totest-copilot-restore-memory-custom-job.mdbut for the sandbox memory limit rather than cache-memory).New fixtures or secrets needed
None.
Notes
Not to be confused with
cache-memory/restore-memory(already covered bytest-copilot-restore-memory-custom-job.md). This targets the separatesandbox.agent.memoryfield that maps to--memory-limit. Primary value is confirming the lock file actually contains--memory-limit 2gand that the run doesn't fail (e.g. OOM/exit 137) — could be checked via a follow-up grep on the generated.lock.ymlrather than requiring live verification.