[CI failure] CI on rage/277-planner-protocol-context #282

New issue

Closed

opened 2026-08-27 18:21:50 +00:00 by github-actions[bot] · 1 comment

github-actions[bot] commented

2026-08-27 18:21:50 +00:00

(Migrated from github.com)

Automated prolog-rlm workflow failure report.

Workflow: CI
Run: https://github.com/lost-rob0t/prolog-rlm/actions/runs/33102970883
Branch: rage/277-planner-protocol-context
Commit: c813df0f45886f4c09127cfb5d7531eae3af5f22
Event: pull_request
Attempt: 1
Conclusion: failure
Pull request: #278

This issue is deduplicated by workflow + branch. Close it after the failure is resolved; a later regression will open a new issue.

Generated by .github/workflows/report-workflow-failures.yml.

Automated prolog-rlm workflow failure report. - Workflow: `CI` - Run: https://github.com/lost-rob0t/prolog-rlm/actions/runs/33102970883 - Branch: `rage/277-planner-protocol-context` - Commit: `c813df0f45886f4c09127cfb5d7531eae3af5f22` - Event: `pull_request` - Attempt: `1` - Conclusion: `failure` - Pull request: #278 This issue is deduplicated by workflow + branch. Close it after the failure is resolved; a later regression will open a new issue. _Generated by `.github/workflows/report-workflow-failures.yml`._

nsaspy commented

2026-09-02 17:26:26 +00:00

Owner

CI run on rage/277-planner-protocol-context: PR #278 was closed unmerged (superseded by the merged #286 prolog-rlm-v1 consolidation), so this branch lane can never turn green. Exact-head acceptance tracking remains in #277/#279.

nsaspy closed this issue

2026-09-04 14:36:18 +00:00