Version 2.8.4 Still continues to Generate an Empty Coverage File
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 39/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ruby
- Domain
- testing-qa
Research direction
Compare the coverage output from Slather 2.8.0 with 2.8.1 and later, using the reported .slather.yml keys and command as the reproduction. Start by reading issue 561 and tracing the coverage command's handling of build_directory, ignore, and profdata input; identify where the report becomes []. Done means the same setup produces a nonempty report.json on the affected versions.
Written by the indexing model from the issue text.
Description
I am still experiencing the empty coverage report issue described here: https://github.com/SlatherOrg/slather/issues/561 , even after upgrading to 2.8.4.
Specifically we have a .slather.yml file which uses the keys: build_directory and ignore .
We then run slather with the following command. bundle exec slather coverage --input-format 'profdata' --scheme <our_scheme> --workspace <absolute_path_to_workspace> --source-files <glob_with_absolute_path> --binary-file <absoluted_path_to_binary_file> <absolute_path_to_xcodeproj> On version 2.8.0 , this works fine for us. On 2.8.1+ it outputs an empty report.json file. I've tried in 2.8.1, 2.8.2, and 2.8.4. Specifically the output of the report is always []
I've tried using both Xcode 15.4 and 16.0 if that matters.
- 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 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
SlatherOrg/slather#586 · 4 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
-
bug f:search
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
manyfold3d/manyfold#7346 · 1 comment ·
Maintainers usually reply within 1 day
-
🐞 bug pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CircuitVerse/CircuitVerse#8025 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
we-promise/sure#4199 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
riscv/riscv-unified-db#2738 ·
Maintainers usually reply within 1 day