Support for path equivalence/relocation.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Read the path-equivalence proposal in linked issue #547 and trace how Slather invokes llvm-cov for coverage reports. Determine where path remapping belongs in that invocation and how it should work with the demonstrated --source-directory and binary arguments. Done means coverage reports can resolve source files when the build and reporting trees use different paths; the issue names no files or tests.
Written by the indexing model from the issue text.
Description
We're using slather for coverage reporting on CI, and in our case the job that runs coverage does not have access to the source tree at the exact location used for building the project. As a result, currently slather fails to produce the expected reports because llvm-cov complaints "Source file does not exist, proceeded by ignoring it".
bundle exec slather coverage --sonarqube-xml --verbose --scheme Foo --input-format profdata --source-directory . --binary-file DerivedData/YYY/Build/Products/Debug-iphonesimulator/ZZZ/ZZZ.framework/ZZZ --build-directory .DerivedData --arch arm64 Pods/Pods.xcodeproj
Slathering...
Processing coverage file: /XXX/DerivedData/Marktplaats/Build/ProfileData/67DAEC2E-11AB-4752-A18D-98187A5CE519/Coverage.profdata
Against binary files:
DerivedData/YYY/Build/Products/Debug-iphonesimulator/ZZZ/ZZZ.framework/ZZZ
warning: /MMM/Modules/Foo/Sources/Foo/Dependencies/Bar.swift: Source file doesn't exist, proceeded by ignoring it.
From what I learned, to solve this, we need support for path-equivalence in llvm-cov, the idea is illustrated in #547.
- Dominant language
- Ruby
- Stars
- 1.6k
- Forks
- 239
- Avg merge
- 10h 19m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SlatherOrg/slather
-
2.8.6: NoMethodError "undefined method 'first'" in profdata_coverage_dir whenever --scheme is usedPossibly taken @MirekNalepa claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
SlatherOrg/slather#586 · 3 comments · 4 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
SlatherOrg/slather#582 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
SlatherOrg/slather#580 · 9 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 56/100
SlatherOrg/slather#578 · 3 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
SlatherOrg/slather#577 ·
All issues in SlatherOrg/slather
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
ETQ admin, le select de condition d'une annotation répétable liste les champs publics deux foisOpen
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
demarche-numerique/demarche.numerique.gouv.fr#14301 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
voxpupuli/puppet-powerdns#251 ·
-
needs verification
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days