Added github-actions reporter to vitest CI runs#28008
Conversation
- vitest's `dot` reporter emits its progress and failure summary as one huge single-line stream; GitHub truncates it, so CI logs never show which test actually failed - the `github-actions` reporter emits inline `::error::` annotations pinned to the failing file and line; gated on GITHUB_ACTIONS so local runs keep the compact dot-only output
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThis PR modifies the Vitest configuration in Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
vitest's
dotreporter writes its progress and its failure summary as one continuous single-line stream. GitHub Actions truncates long log lines, so when a vitest test fails in CI the summary block (⎯⎯ Failed Tests ⎯⎯, the test name, the assertion diff) gets cut off — the logs show the step exited 1, but not which test failed.This adds the
github-actionsreporter alongsidedot, gated onGITHUB_ACTIONSso local runs keep the compact dot-only output. The reporter emits inline::error::annotations pinned to the failing file and line, which surface directly on the job and the PR diff.Found while debugging a unit-test failure on another PR, where the truncated log made it impossible to identify the failing test without reproducing the whole suite locally.
🤖 Generated with Claude Code