Suggested test: copilot/runtimes-elixir

[github-actions]

Motivation

Link to the gh-aw PR: github/gh-aw#44283 — fix: expose erl in AWF sandbox when using runtimes.elixir

PR #44283 added Elixir runtime support to the AWF sandbox: it emits a Capture ERLANG_HOME step after erlef/setup-beam and prepends ERLANG_HOME/bin to PATH inside the chroot, so mix can find erl. There is no E2E test exercising the Elixir runtime path.

Proposed test

• Workflow file: test-copilot-runtimes-elixir.md
• Trigger: workflow_dispatch
• Engine: copilot
• Safe output: create-issue
• Variant: standard (sandbox enabled)

Minimal test prompt sketch

Declare runtimes.elixir: true in the frontmatter. Ask the agent to run elixir -e "IO.puts(:os.type())" via a command or gh-steps block to verify Elixir is accessible inside the sandbox, then create an issue reporting the output. The test passes if the issue body contains the expected Elixir output (e.g. {:unix, :linux}).

New fixtures or secrets needed

None — the Elixir runtime is provided by the AWF sandbox machinery (erlef/setup-beam). No additional secrets or repos are required.

Notes

The existing test-copilot-gh-steps.md provides a model for how to exercise shell commands inside the sandbox and capture output to a safe-output. The Elixir test would be similar but specifically validates the ERLANG_HOME injection from #44283. If runtimes.elixir is a rarely-used feature, a nosandbox variant may not be needed.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 🔍 Suggest New E2E Tests · 97.4 AIC · ⌖ 8.19 AIC · ⊞ 5.6K · ◷