Ruby on Rails Tuesday, June 26, 2012

On Monday, June 25, 2012 10:58:47 PM UTC-7, Mandy wrote:

I am using Rails 2.3.8 application and when I enter rake command it
gives following error :

ms@ms-HP:~/OpenStreetView$ rake
WARNING: 'require 'rake/rdoctask'' is deprecated.  Please use 'require
'rdoc/task' (in RDoc 2.4.2+)' instead.
    at /home/ms/.rvm/gems/ruby-1.9.3-p194@global/gems/rake-0.9.2.2/lib/rake/rdoctask.rb
rake aborted!
(<unknown>): did not find expected node content while parsing a flow
node at line 18 column 14

(See full trace by running task with --trace)

Please help me to solve this problem.

My best guess is that this is due to a rake version problem. The installed rake in your system is probably not the intended version for running your Rakefile. Are you using bundler or rvm?

 

And I also check rake command in Rails 3.2.6 application. Then it
gives following result :

ms@ms-HP:~/Desktop/rails3/blog$ rake
Run options:

# Running tests:



Finished tests in 0.004364s, 0.0000 tests/s, 0.0000 assertions/s.

0 tests, 0 assertions, 0 failures, 0 errors, 0 skips
Run options:

# Running tests:

.FFF.F.E

Finished tests in 0.671677s, 11.9105 tests/s, 11.9105 assertions/s.

  1) Failure:
test_should_create_post(PostsControllerTest)
[/home/ms/Desktop/rails3/blog/test/functional/posts_controller_test.rb:20]:
"Post.count" didn't change by 1.
<3> expected but was
<2>.

  2) Failure:
test_should_destroy_post(PostsControllerTest)
[/home/ms/Desktop/rails3/blog/test/functional/posts_controller_test.rb:43]:
"Post.count" didn't change by -1.
<1> expected but was
<2>.

  3) Failure:
test_should_get_edit(PostsControllerTest)
[/home/ms/Desktop/rails3/blog/test/functional/posts_controller_test.rb:34]:
Expected response to be a <:success>, but was <401>

  4) Failure:
test_should_get_new(PostsControllerTest)
[/home/ms/Desktop/rails3/blog/test/functional/posts_controller_test.rb:16]:
Expected response to be a <:success>, but was <401>

  5) Error:
test_should_update_post(PostsControllerTest):
ActionController::RoutingError: No route matches {:action=>"show",
:controller=>"posts", :id=>nil}
    /home/ms/.rvm/gems/ruby-1.9.3-p194/gems/actionpack-3.2.6/lib/action_dispatch/routing/route_set.rb:532:in
`raise_routing_error'
    /home/ms/.rvm/gems/ruby-1.9.3-p194/gems/actionpack-3.2.6/lib/action_dispatch/routing/route_set.rb:528:in
`rescue in generate'
    /home/ms/.rvm/gems/ruby-1.9.3-p194/gems/actionpack-3.2.6/lib/action_dispatch/routing/route_set.rb:520:in
`generate'
    /home/ms/.rvm/gems/ruby-1.9.3-p194/gems/actionpack-3.2.6/lib/action_dispatch/routing/route_set.rb:561:in
`generate'
    /home/ms/.rvm/gems/ruby-1.9.3-p194/gems/actionpack-3.2.6/lib/action_dispatch/routing/route_set.rb:586:in
`url_for'
    /home/ms/.rvm/gems/ruby-1.9.3-p194/gems/actionpack-3.2.6/lib/action_dispatch/routing/url_for.rb:148:in
`url_for'
    /home/ms/.rvm/gems/ruby-1.9.3-p194/gems/actionpack-3.2.6/lib/action_dispatch/routing/route_set.rb:213:in
`post_path'
    /home/ms/.rvm/gems/ruby-1.9.3-p194/gems/actionpack-3.2.6/lib/action_dispatch/testing/assertions/routing.rb:174:in
`method_missing'
    /home/ms/Desktop/rails3/blog/test/functional/posts_controller_test.rb:39:in
`block in <class:PostsControllerTest>'

8 tests, 8 assertions, 4 failures, 1 errors, 0 skips
Errors running test:functionals! #<RuntimeError: Command failed with
status (5): [/home/ms/.rvm/rubies/ruby-1.9.3-p194/bin/r...]>

Here, the rake command is doing what it's supposed to: Running the tests. The tests are failing, but that is not a problem with rake, it's just that the rails application doesn't behave the way the test expect it to. 

-- 
Ylan

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/fP1wica2nbMJ.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

No comments:

Post a Comment