-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No such file or directory - tmp/metric_fu/scratch/rcov/rcov.txt #87
Comments
For full trace of the error: http://pastebin.com/LGAKnemG |
did you try running rcov outside of metric fu? this might be an issue there. |
yes, I tried, but the issue is still the same, anyway I switched to REE |
Good work, knuckleheads. Love it when you close unfixed bugs. |
@nello that really doesn't help things. I might suggest a more positive approach of opening an issue with a reproducible example. This issue was closed because it is against an old version of RCov and nobody had a concrete example to test against. |
You're absolutely right, and I regretted it as soon as I had typed it. :-( I'll try to put together an example tonight, but it certainly appears to be broken for me on 1.9.3. Nello I'm living so far beyond my income that we may almost be said to be living apart.
On 30/04/2012, at 1:47:47PM, Aaron Bedra wrote:
|
You're right! It is broken on 1.9.3. It will never work on 1.9.x. If you take glance at the README you will notice the following: RCov - Code Coverage for Ruby Why? What? This is our fork of Mauricio Fernandez's RCov (maintained by Relevance). NOTE: This fork does not work on Ruby 1.9.x. For coverage on Ruby 1.9 look at SimpleCov. |
Hello
Environment:
jRuby-1.6.5 / Rails 2.3.8 / rcov 0.9.3
Command line:
** Running the specs/tests in the [test] environment
The command line is too long.
rake aborted!
No such file or directory - tmp/metric_fu/scratch/rcov/rcov.txt
(See full trace by running task with --trace)
Actually I tried even create rcov.txt file but didn't work at all, it seems like rcov deletes this file
The text was updated successfully, but these errors were encountered: