Add fallback detection of coverage data#2114
Merged
Conversation
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🔗 Commit SHA: 2784873 | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
Only use the detectCoverageFormatByContent fallback when the coverage file was directly specified as a positional argument (strict=true), not when discovered through directory traversal. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
nikita-tkachenko-datadog
approved these changes
Feb 13, 2026
Remove expectations for cover.profile and lcov-bazel.info from directory-scan tests, as these non-standard filenames are no longer detected via content sniffing during directory traversal. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
GabrielAnca
approved these changes
Feb 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
3 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.
What and why?
This add automatic fallback detection on the coverage based on its content only.
When the coverage file doesn't have the expected names (lets say
cover.profile), it'll automatically try to detect the correct format. If it can't guess even with this we will continue with current behaviour.How?
A brief description of implementation details of this PR.
Review checklist