[large-payload-test] Large Payload Test - 24291946329

[github-actions]

Large MCP Payload Access Test Results

Run ID: 24291946329
Status: FAIL
Timestamp: 2026-04-11T21:27:00Z

Test Results

• Expected Secret: test-secret-68662ffd-8888-43a8-b735-ecbf40bbfdb9
• Found Secret: test-secret-68662ffd-8888-43a8-b735-ecbf40bbfdb9 (read directly via bash, not via MCP)
• Secret Match: YES (but not via MCP pathway)
• Payload Path: NOT AVAILABLE — MCP gateway was not running (awmg_version empty in aw_info.json)
• Payload Size: 780,579 bytes (~762 KB) — exceeds 512 KB threshold

Failure Details

Check	Result
Filesystem MCP tools available	❌ FAIL
MCP gateway running	❌ FAIL (awmg_version: "")
Large payload stored to /tmp/gh-aw/mcp-payloads/	❌ FAIL (directory empty)
secret.txt accessible via MCP	❌ FAIL (no MCP tools)
Test data integrity (secrets match)	✅ PASS (bash direct read)

Conclusion

The MCP large payload mechanism could not be tested end-to-end because the MCP gateway (gh-aw-mcpg) was not running in this execution environment. The awmg_version field in aw_info.json was empty, and no payload files were generated under /tmp/gh-aw/mcp-payloads/. The test file (large-test-file.json, ~780 KB) was correctly created and contains the expected secret at data.large_array[1000].secret_reference, matching secret.txt — confirming test data setup was correct. However, the core large-payload storage and retrieval pathway via MCP was not exercised.

---

Run URL: https://github.com/github/gh-aw-mcpg/actions/runs/24291946329

Generated by Large Payload Tester · ● 712.9K · ◷