chore(ci): Remove codecov steps from jobs that produce no coverage/JUnit data#20244
Merged
chore(ci): Remove codecov steps from jobs that produce no coverage/JUnit data#20244
Conversation
…t data Several CI jobs were running `getsentry/codecov-action` despite not producing any coverage or JUnit XML files, causing noisy warnings in every CI run: - Node integration tests: coverage disabled in vitest config, custom reporters without JUnit output - Node-core integration tests: same as above - E2E tests: use ts-node/Playwright, not vitest — no coverage or JUnit - Remix tests: custom vitest config without coverage or JUnit reporter Also disables coverage upload for Playwright browser integration tests (both regular and loader), which only produce JUnit XML but not coverage files. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Core
Deps
Other
Bug Fixes 🐛Deno
Other
Internal Changes 🔧Deps
Other
🤖 This preview updates automatically when you update the PR. |
mydea
changed the title
Contributor
size-limit report 📦
|
Contributor
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
Member
Author
|
Related: getsentry/codecov-action#77 |
Lms24
approved these changes
Apr 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
getsentry/codecov-actionfrom CI jobs that don't produce coverage or JUnit XML files, eliminating noisy warnings in every CI runJobs cleaned up:
enable-coverage: falseenable-coverage: falseWarnings eliminated:
No coverage files found(from integration tests, E2E, Remix, Playwright jobs)No JUnit XML files found matching pattern: dev-packages/{node,node-core}-integration-tests/**/*.junit.xmlNo JUnit XML files found matching pattern: dev-packages/e2e-tests/**/*.junit.xmlPlease ensure your test framework is generating JUnit XML outputSupported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecovNot addressed (upstream issue):
Entity expansion limit exceeded: 100X > 1000on vitest JUnit XML files — this is a parser limitation ingetsentry/codecov-actionthat affects large test suites (browser, core, node, nextjs, etc.)Test plan
🤖 Generated with Claude Code