../ runs index

Campaign a2a-hermes-v0.6.2-rc.0-v3r5 FAIL

Agent group
hermes (homogeneous)
ai-memory ref
v0.6.2-rc.0
Completed at
2026-04-22T11:03:34Z
Overall pass
false
Skipped reports
0

Infrastructure

Provider
digitalocean
Region
nyc3
Droplet size
s-2vcpu-4gb
Topology
4-node federation mesh (W=2/N=4)
Scenarios started
Scenarios ended
Dispatched by
alphaonedev
Harness SHA
1d6f036b7bb6
Workflow run
https://github.com/alphaonedev/ai-memory-ai2ai-gate/actions/runs/24774789925

Node roster

#RoleAgent IDPublic IPPrivate IP
1agentai:alice
2agentai:bob
3agentai:charlie
4memory-only

Run focus

Campaign failed: no scenario reports recovered.

What this campaign tested: No scenarios were exercised; requested 35 scenarios covering various transport, framework, and primitive axes, but none reported results.

What it demonstrated: The run proved nothing about AI memory sharing due to complete absence of scenario outcomes.

AI NHI analysis · Claude Opus 4.7

Campaign failed: no scenario reports recovered.

FAIL — zero scenarios executed or reported.

For three audiences

Non-technical end users

This test was supposed to check if AI agents can reliably share memories with each other. Unfortunately, the test didn't run properly, and no results were collected. We don't know from this run if the agents share memories well or not.

C-level decision makers

This campaign failure indicates high risk in the testing pipeline, blocking production readiness assessments for ai-memory v0.6.2-rc.0. Customer-facing claims about reliable agent-to-agent memory federation remain unvalidated. No changes vs. prior runs can be assessed due to zero data.

Engineers & architects

The run aborted without recovering any scenario reports, likely due to a harness or infra provisioning failure in the CI workflow (harness_sha: 1d6f036b7bb68a8ba85760e1f0cb17a7170a1054). All 35 requested scenarios (e.g., S1, S1b, S2) across federation mesh topology were impacted, with probable root cause in report aggregation. No specific primitives or failure modes observable without logs.

What changes going into the next campaign

Debug and fix the report recovery logic in the CI harness to ensure scenario outputs are captured.

All artifacts