Repository navigation
Find Swift Test Coverage in Either Build System's Layout - #39
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 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 |
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
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.
♻️ Current situation & Problem
Swift 6.4's default build system writes its products to
.build/out/Products/<Config>-<platform>, with one<Target>Tests.soper test target instead of a.xctest.The coverage step of
swift-test.ymlonly searched the native layout (.build/<triple>/<config>/codecovand*.xctest), found nothing, andllvm-cov exportfailed with "exactly one of -instr-profile and -empty-profile must be specified".Every caller that sets
artifact_namefails on Swift 6.4 even though its tests pass, for example SchmiedmayerLab/MyHeartCounts-iOS#204.⚙️ Release Notes
-object.📚 Documentation
A two-line comment in the step names both layouts.
✅ Testing
actionlintpasses.The exact step was run in Swift 6.4 on Linux against
MyHeartCountsShared: with the default build system it exports 402 LCOV records from the test.so, and with--build-system native342 records from the.xctest.Code of Conduct & Contributing Guidelines