Slather empty result on Jenkins CI
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ruby
- Domain
- ci-cd, testing-qa
Research direction
Start by reproducing the empty coverage report on Jenkins with the workspace under /var/lib/jenkins, which links to /private/var, and compare it with the working $HOME setup. The report says verbose output shows the same paths to Coverage.profdata and the binary, with no warnings. Identify whether the path or a permissions issue explains the difference, then confirm Slather generates a nonempty report.
Written by the indexing model from the issue text.
Description
For some unknown reason slather v2.6.0 generates empty coverage reports on Jenkins CI. I have setup Jenkins workspace to /var/lib/jenkins, where /var is a link to /private/var. The exact same call to slather (via Fastlane or directly - with slather file or through command params) works fine if the project is placed in the $HOME directory (/Users/dirakto/workspace). Does anybody have any solution?
I used the verbose option and according to the output I am comparing the exact same paths (to Coverage.profdata and binary), and I've granted access to files to my terminal, so my only other idea is that it's either the path's fault or slather/xcodebuild is placing some temp files and there is some permission issue.
Remember that slather is successfully generating the report and doesn't produce any warnings.
- Dominant language
- Ruby
- Stars
- 1.6k
- Forks
- 239
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 2
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
-
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 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
SlatherOrg/slather#576 · 2 comments ·
All issues in SlatherOrg/slather
Similar issues
-
message-patterns
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
sisimai/rb-sisimai#468 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 7 days
-
bugsnag
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
JoeMcB/improvcoaches#827 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
TheOdinProject/curriculum#31465 ·
Maintainers usually reply within 1 day