Show structured command failures in CI log and summary buffers #639

New issue

Closed

opened 2026-05-06 19:55:43 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-05-06 19:55:43 +00:00

Owner

Parent: #634

Problem

CI log and summary buffers currently write trimmed stderr/stdout or generic no log output / no output lines. They drop command identity and exit code, and they hide stdout when stderr exists. This makes failed log fetches hard to diagnose, especially across Forgejo/Gitea action APIs.

Scope

Improve failure rendering in forge.log.open and forge.log.open_summary.
Include bounded command failure context in the buffer.
Reuse shared formatting from #635 where possible.
Add tests for failed log command output.

Non-goals

Do not rewrite CI log parsers.
Do not change successful log rendering/folding.

Parent: #634 ## Problem CI log and summary buffers currently write trimmed stderr/stdout or generic `no log output` / `no output` lines. They drop command identity and exit code, and they hide stdout when stderr exists. This makes failed log fetches hard to diagnose, especially across Forgejo/Gitea action APIs. ## Scope - Improve failure rendering in `forge.log.open` and `forge.log.open_summary`. - Include bounded command failure context in the buffer. - Reuse shared formatting from #635 where possible. - Add tests for failed log command output. ## Non-goals - Do not rewrite CI log parsers. - Do not change successful log rendering/folding.

barrettruth added the

bug

v0.2.0

labels

2026-05-06 19:55:43 +00:00

barrettruth referenced this issue

2026-05-06 19:56:06 +00:00

Tracker: error handling and edge cases #634

barrettruth referenced this issue from a pull request that will close it,

2026-05-06 21:50:35 +00:00

Show CI log command failures with context #652

barrettruth closed this issue