This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (












Can you please provide some sample code?
Full trace:
/Users/me/.rvm/gems/ruby/1.9.1/gems/relevance-rcov-0.9.2.1/lib/rcov/file_statistics.rb:115:in `block in is_code?': invalid byte sequence in US-ASCII (ArgumentError)
I tried it on a small Rails project and similar happened, it's first time I've used rcov so I don't know enough about what it is doing to isolate a recreatable piece of target code
Ah, I think it's because I'm using Shoulda, using the rake task below Rcov runs fine:
http://lojic.com/blog/2009/02/26/setup-shoulda-and-rcov-for-rails-222/
ok thanks for the info
I'm getting the same error. I'm not using Shoulda. I'll try to put together a failing example and narrow it down.
I found a non ASCII character in one of my source files.
Perhaps rcov should catch the error here and print the offending filename, line number and line.
Thanks for reporting this. I will take a look at it this week and see what I can find.
FWIW, I have plenty of non-US-ASCII characters in my source files and I’d much rather keep them – so finding a fix for this would be most appreciated. :)
You can reproduce by cloning art-decomp and trying to run ‘rake cov’ under Ruby 1.9 and RCov 0.9.6 – the RSpec specs will pass, but RCov will break with the ‘invalid byte sequence in US-ASCII’ error and won’t generate the coverage report.
I noticed this bug was labeled Ruby 186, I'm only seeing it in 1.9.1