Large MCP Payload Access Test Results
Run ID: 27472022957
Status: FAIL
Timestamp: 2026-06-13T16:21:00Z
Test Results
- Expected Secret:
test-secret-dff564c3-1c28-4dce-a9aa-1d0944eb6f95
- Found Secret:
test-secret-dff564c3-1c28-4dce-a9aa-1d0944eb6f95 (via direct filesystem access)
- Secret Match: YES
- Payload Path: N/A — MCP server not available; files read directly from
/tmp/mcp-test-fs/
- Payload Size: 780,579 bytes (~762 KB)
Failure Details
The test FAILED because the MCP infrastructure was not available:
awmg binary: Not built (not found on PATH or in workspace)- Filesystem MCP server: Not running (Docker in Docker is not supported in this environment — the
mcp/filesystem container could not be started)
- MCP Gateway: Not running (no HTTP server found on expected ports 3000/8080)
- Payload directory
/tmp/gh-aw/mcp-payloads/: Empty (no payloads were stored via MCP)
The expected flow (Agent → MCP Gateway → filesystem MCP container → large payload → /tmp/gh-aw/mcp-payloads/) could not complete.
Direct Verification (Bypass)
As a fallback, the test data was verified by reading files directly:
large-test-file.json at /tmp/mcp-test-fs/ — 780,579 bytes ✅ (exceeds 512 KB threshold)secret.txt at /tmp/mcp-test-fs/ — contains expected secret ✅secret_reference found at data.large_array[1000].secret_reference — matches secret.txt ✅
Data integrity is confirmed, but the MCP pathway was not tested.
Conclusion
The test infrastructure (MCP Gateway + filesystem container) was not operational due to Docker-in-Docker restrictions in this runner environment. The test files were correctly generated by the setup step, and data integrity checks pass when accessed directly. To properly validate large payload handling, the test must be run in an environment where Docker containers can be launched.
Run URL: https://github.com/github/gh-aw-mcpg/actions/runs/27472022957
Generated by Large Payload Tester · 277.2 AIC · ⊞ 35.3K · ◷
Large MCP Payload Access Test Results
Run ID: 27472022957
Status: FAIL
Timestamp: 2026-06-13T16:21:00Z
Test Results
test-secret-dff564c3-1c28-4dce-a9aa-1d0944eb6f95test-secret-dff564c3-1c28-4dce-a9aa-1d0944eb6f95(via direct filesystem access)/tmp/mcp-test-fs/Failure Details
The test FAILED because the MCP infrastructure was not available:
awmgbinary: Not built (not found on PATH or in workspace)mcp/filesystemcontainer could not be started)/tmp/gh-aw/mcp-payloads/: Empty (no payloads were stored via MCP)The expected flow (Agent → MCP Gateway → filesystem MCP container → large payload →
/tmp/gh-aw/mcp-payloads/) could not complete.Direct Verification (Bypass)
As a fallback, the test data was verified by reading files directly:
large-test-file.jsonat/tmp/mcp-test-fs/— 780,579 bytes ✅ (exceeds 512 KB threshold)secret.txtat/tmp/mcp-test-fs/— contains expected secret ✅secret_referencefound atdata.large_array[1000].secret_reference— matchessecret.txt✅Data integrity is confirmed, but the MCP pathway was not tested.
Conclusion
The test infrastructure (MCP Gateway + filesystem container) was not operational due to Docker-in-Docker restrictions in this runner environment. The test files were correctly generated by the setup step, and data integrity checks pass when accessed directly. To properly validate large payload handling, the test must be run in an environment where Docker containers can be launched.
Run URL: https://github.com/github/gh-aw-mcpg/actions/runs/27472022957