Couldn't parse the number of tests from the output about scan HOT 13 CLOSED

Oh I see where the error occurs.

if result[:failures] > 0
  failures_str = result[:failures].to_s.red
else
  failures_str = result[:failures].to_s.green
end

My tests pass so result[:failures] is nil 😏 I'll have a look at a pull request for you tomorrow.

from scan.

I've tried to replicate this across 3 machines. Only 1 exhibits the behaviour.

Ruby 2.0.0p481 (default Ruby in Yosemite) ✔️
Ruby 2.2.1p85 (default Ruby in El Cap) ✔️
Ruby 2.2.3p173 (i have no idea where I installed this from /usr/local/bin/ruby) ✖️
Ruby 2.2.3p173 (installed with rbenv) ✔️

Closing this as I think its definitely an issue with my machine rather than scan.

from scan.

In case someone else runs across this, I ran into this same error message trying to get scan to run. I was able to fix it by upgrading to Ruby 2.2.1p85 from Ruby 2.0.0. I then reinstalled scan and fastlane.

It may be a red herring, but my initial install of the tools did run into issues that I worked around based on fastlane/fastlane#338. My reinstall worked flawlessly without this workaround.

from scan.

Interesting that you got it on Ruby 2.0.0 was this system ruby or rbenv/chruby/rvm?

from scan.

I'd say probably system Ruby that came installed with Yosemite. I used rvm to get Ruby 2.2.1. And that's about the extent of my ruby knowledge. ;)

from scan.

Interesting... @squarefrog did you find the source of this issue?

from scan.

I thought I had, but it turned out it was just an odd install.

I'm scratching my head about this. It's only that install that I had difficulty with. I use a shared GEM_HOME so it's not even like there was something wrong with the gem.

Diffing the broken run log against a working one doesn't appear to show anything untoward.

I don't know if you can shed any more light on the flow after the build? It looked like it was just tee'd into xcpretty then the output scraped with scan.

I can't immediately see any points of failure. Shoot me a DM on Twitter if you want me to send the logs.

from scan.

I'm running into this problem also but only via running fastlane, running scan directly seems to work fine. I have ruby version ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin15] via homebrew

Looks like I'm seeing the error running scan directly via jenkins also on a different server with the same version of ruby.

from scan.

I have the same issue on ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-darwin14] installed via RVM

from scan.

I fixed this by updating ruby and ruby gem:
rbenv install 2.2.2
rbenv global 2.2.2
gem update --system

from scan.

I'm seeing this error at the start of running scan:

Loading...
tee: /Users/kevin.harwood/Library/Logs/scan/MyKit-MyKit.log: Permission denied

Followed by this at the end:

cat: /Users/kevin.harwood/Library/Logs/scan/MyKit-MyKit.log: No such file or directory
[08:11:47]: Couldn't parse the number of tests from the output

from scan.

It looks like /Users/kevin.harwood/Library/Logs/scan may have been created a while ago when I ran scan against another project, most likely with scan install via a different mechanism. Removing that directory, and letting scan recreate it seems to have worked for me.

from scan.

This issue was migrated to fastlane/fastlane#3369. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀

from scan.