You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@Dirakto did you ever get a solution to this, I think I'm running into the same issue.
we seem to have figured out the issue is that xcrun llvm-cov show -instr-profile works with /var but not /private/var so trying to figure out a different solution.
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.
The text was updated successfully, but these errors were encountered: