← Back to issue list

Properly log spread output on testing service

View original Github issue

Metadata

Project
craft-application
Number
#715
Type
issue
State
closed
Author
tigarmo
Labels
—
Created
Updated
Closed

Current evaluation

Spread logging request was closed without a linked fix; the only follow-up was automated creation of internal ticket CRAFT-4411.

Resolution: closed stale

Reason: #715 was closed after 541 days without further activity, a linked commit or PR, or a maintainer explanation. The sole recorded follow-up was automated Jira ticket CRAFT-4411.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### What needs to get done Currently we just pause the emitter when calling `spread`; this means that the output shows up on the terminal only. ### Why it needs to get done So that the messages get properly logged and let us "one-line" the messages in brief mode.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed stale Spread logging request was closed without a linked fix; the only follow-up was automated creation of internal ticket CRAFT-4411.
stealth/space-bunny-alpha — closed stale Spread logging request was closed without a linked fix; the only recorded follow-up was automatic creation of internal ticket CRAFT-4411.
qwen/qwen3.6-35b-a3b — — Closed without a public fix. Tracking was deferred to internal Jira ticket CRAFT-4411. No code changes, merges, or resolutions were implemented.
qwen/qwen3.6-35b-a3b — — Closed without implementation. Superseded by internal Jira ticket CRAFT-4411 for tracking spread output logging improvements. No code changes or pull requests were merged.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The request to log spread output on the testing service received only an automated Jira sync comment. No fix or pull request was merged, indicating the task was abandoned or moved to internal tracking.

Update history

No update history recorded yet.

Related work

  • Related To: warthogs#4411 (confidence 90%)

    An automated comment created internal Jira ticket CRAFT-4411, but no resolution was recorded.

Related issues

No related issues found above the similarity threshold.