ci: remove non docker tests#834
Conversation
📝 WalkthroughWalkthroughThe PR removes the ChangesParallel Workflow and Coverage
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 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 |
SoWieMarkus
left a comment
There was a problem hiding this comment.
The purpose of test-without-docker is to act as a fast-fail gate by running the tests without spinning up any docker containers and catches obvious failures quickly (and cheaply) before the heavier test-with-docker job is triggered.
I don't have a problem with rremoving this gate. But if we do, the test-without-docker job becomes redundant, so we could drop it entirely. We just need to scope the test-with-docker job to cover the whole repository and not just the ./internal/... directory.
Remove redundant test-without-docker job and expand the Docker-based test job to cover the entire repository (./...) instead of only ./internal/..., as suggested in PR review.
Test Coverage ReportTest Coverage 📊: 69.2% |
No description provided.