Bug Report
Description
Problem Statement
The rebuild-hermes and rebuild-hermes-stale-base nightly E2E jobs failed because the test fixture in test/e2e/test-rebuild-hermes.sh has an empty agentRender array ('agentRender': []) in the expected compiled plan for the Discord channel. Commit 80de9f0 migrated NemoClaw to plan-backed channel state where ManifestCompiler.compile() produces agentRender entries for each channel — specifically three Discord entries (discord-hermes-env, discord-hermes-config, discord-hermes-platform) — but the E2E fixture was not updated. After a sandbox rebuild, the compiled plan contains these entries but the test expects an empty list, causing the assertion to fail:
FAIL: compiled plan mismatch after rebuild — agentRender entries differ
Proposed Design
Populate the agentRender array in the test fixture at line 279 of test/e2e/test-rebuild-hermes.sh with the three Discord render entries that ManifestCompiler.compile() produces for the Hermes agent, matching the structure defined in src/lib/messaging/channels/discord/manifest.ts (lines 127–167):
discord-hermes-env (kind: env-lines, target: ~/.hermes/.env) — Discord bot token, guild IDs, allowed users
discord-hermes-config (kind: json-fragment, target: ~/.hermes/config.yaml, path: discord) — mention, channels, threading, reactions
discord-hermes-platform (kind: json-fragment, target: ~/.hermes/config.yaml, path: platforms.discord) — enabled flag
Alternatives Considered
None — the fixture must match compiler output; there is no alternative structure.
Category
test_failure
Reproduction Steps
- Check out NemoClaw at commit
a3ae21b6eed8399099fd390bd45ad43e78218258
- Run the
rebuild-hermes or rebuild-hermes-stale-base E2E scenario
- Observe that the compiled plan comparison fails on
agentRender
Environment
- OS: GitHub Actions runner (Ubuntu 22.04)
- Node.js: v22.16+
- Docker: Docker-in-Docker (GitHub Actions)
- NemoClaw: main @
a3ae21b
- Other: Nightly E2E run 27386272836
Debug Output
N/A — CI job logs available at https://github.com/NVIDIA/NemoClaw/actions/runs/27386272836
Logs
FAIL: compiled plan mismatch after rebuild — agentRender entries differ
Expected agentRender to contain 3 Discord render entries, got 0
Checklist
Suggested Labels
nightly-e2e, auto-diagnosed, test-failure, hermes, e2e
Suggested Labels (apply manually after triage)
nightly-e2e, auto-diagnosed, test-failure, hermes, e2e
Related PR: #5260
Bug Report
Description
Problem Statement
The
rebuild-hermesandrebuild-hermes-stale-basenightly E2E jobs failed because the test fixture intest/e2e/test-rebuild-hermes.shhas an emptyagentRenderarray ('agentRender': []) in the expected compiled plan for the Discord channel. Commit80de9f0migrated NemoClaw to plan-backed channel state whereManifestCompiler.compile()producesagentRenderentries for each channel — specifically three Discord entries (discord-hermes-env,discord-hermes-config,discord-hermes-platform) — but the E2E fixture was not updated. After a sandbox rebuild, the compiled plan contains these entries but the test expects an empty list, causing the assertion to fail:Proposed Design
Populate the
agentRenderarray in the test fixture at line 279 oftest/e2e/test-rebuild-hermes.shwith the three Discord render entries thatManifestCompiler.compile()produces for the Hermes agent, matching the structure defined insrc/lib/messaging/channels/discord/manifest.ts(lines 127–167):discord-hermes-env(kind:env-lines, target:~/.hermes/.env) — Discord bot token, guild IDs, allowed usersdiscord-hermes-config(kind:json-fragment, target:~/.hermes/config.yaml, path:discord) — mention, channels, threading, reactionsdiscord-hermes-platform(kind:json-fragment, target:~/.hermes/config.yaml, path:platforms.discord) — enabled flagAlternatives Considered
None — the fixture must match compiler output; there is no alternative structure.
Category
test_failure
Reproduction Steps
a3ae21b6eed8399099fd390bd45ad43e78218258rebuild-hermesorrebuild-hermes-stale-baseE2E scenarioagentRenderEnvironment
a3ae21bDebug Output
Logs
Checklist
Suggested Labels
nightly-e2e,auto-diagnosed,test-failure,hermes,e2eSuggested Labels (apply manually after triage)
nightly-e2e,auto-diagnosed,test-failure,hermes,e2eRelated PR: #5260