Chunk pathnames_per_binary into segments that do not exceed the OS ARG_MAX size for calls to llvm-cov

[weibel]

I have encountered the issue in #243 which is not easily solvable. This is an attempt to fix the problem by chunking calls llvm cov into smaller segments which are recombined. I'll give it some time to see if there are any problems.

[coveralls]

Coverage increased (+0.08%) to 95.72% when pulling ba4e9b1 on weibel:master into 1bb36e4 on SlatherOrg:master.

[dnedrow]

@weibel , please be sure to fix up the unit testing so coverage doesn't fall.

[weibel]

@dnedrow Coverage is back up.

[ksuther]

Thanks for this! Looks good to me, but it'd be nice to have confirmation from someone who was encountering the original problem. @diaojunxian, could you see if this solves the problem you encountered?

[weibel]

My main concerns with this is

• I don't have a good solution if getconf ARG_MAX does not work on the system
• The effective usable size of an argument is harder to determine than the 10% padding I have put in https://www.in-ulm.de/~mascheck/various/argmax/

[weibel]

I have addressed my concerns with ba4e9b1

[ksuther]

Thanks @weibel!

[stevebaxter]

Any chance of a release that includes this fix sometime soon? We're running in to this issue!

[mrdjtoto]

Hello,
I am facing the same problem on one of my code coverage calculation. I've performed the unit test in fastlane with scan (calling them all from Jenkins) and then I am using slather to get the code coverage in llcov format. This is the command and the following output:

slather coverage --jenkins --llvm-cov --build-directory ./DerivedData --binary-basename 'My App Mobile' --output-directory ./sonar-reports --scheme MYA_UAT --workspace MyApp.xcworkspace MyApp.xcodeproj
/Users/vobadm/.rvm/gems/ruby-2.4.2/gems/slather-2.4.7/lib/slather.rb:26: warning: Insecure world writable dir /change in PATH, mode 040777
Slathering...
sh: /usr/bin/xcrun: Argument list too long
Slathered

I'm running on xcode 11.3

Is there a way to get through this? I've read about this fix. Will it be released sometime soon? Thank you so much.