[rspec-users] drbspec - "no server running"

aslak hellesoy aslak.hellesoy at gmail.com
Mon Feb 26 02:52:42 EST 2007


On 2/26/07, Scott Taylor <mailing_lists at railsnewbie.com> wrote:
>
> On Feb 26, 2007, at 12:41 AM, aslak hellesoy wrote:
>
> > On 2/26/07, Scott Taylor <mailing_lists at railsnewbie.com> wrote:
> >>
> >> I've created a little 30 second screen cast to show the problem:
> >>
> >
> > Hey, that's a neat bug report format!
> >
>
> Well, there is nothing quite like sitting in a room with someone to
> watch them reproduce the bug; words can be vague.  I suppose that
> this is the closest I'll get to that ideal bug report...(at least
> over the internet).  Plus, I've been looking to put that $70 that
> I've spent on screencasting software to work.
>
> I have my project svn'ed, with an externals on the rspec and
> rspec_on_rails repositories.  I'm at revision 1536 - Is this correct
> for RC1?  Do I also need to update the gem?
>

Yes - like it's described on the announcement I linked to.

> Best,
>
> Scott
>
>
>
>
>
>
>
> > Please try to uninstall your current RSpec release and install 0.8 RC1
> > release - I think your problem will be gone.
> >
> > http://www.nabble.com/-ANN--RSpec-0.8.0-RC1-t3245509.html
> >
> > In 0.8 you have to say spec --drb instead of drbspec (see the
> > release notes)
> >
> > Also, for the future, please remember to tell us what versions of
> > OS/Ruby/RSpec/Rails you're running. (ok, I could see you have a mac
> > :-)
> >
> > HTH,
> > Aslak
> >
> >> http://railsnewbie.com/files/screencasts/rspec_on_rails-
> >> no_server_running.mov
> >>
> >> All I did before this, as I've said in the previous email, was
> >> generate a controller with:
> >>
> >> ./script/generate rspec_controller -c CollectiveDictionary index show
> >>
> >> Best,
> >>
> >> Scott
> >>
> >>
> >> On Feb 25, 2007, at 9:22 PM, Scott Taylor wrote:
> >>
> >>>
> >>> At times I've gotten the message "No Server Running" from drbspec
> >>> with my rails app.  The thing is, the drb server certainly is
> >>> running!
> >>>
> >>> This happened a few times with my model specs.  I'm not sure exactly
> >>> what the problem was there - I believe I was loading up fixtures
> >>> that
> >>> didn't exist.  I was calling fixtures :singular_table_name as
> >>> opposed
> >>> to fixtures :plural_table_name
> >>>
> >>> This time it happened with my controller.  I generated the
> >>> controller
> >>> with the ./script/generate rspec_controller ControllerName
> >>> command...
> >>>
> >>> It doesn't appear that the specs are setup to fail to begin with,
> >>> but
> >>> if this were the default behavior, one certainly shouldn't see a "No
> >>> Server Running"
> >>>
> >>> I could create a short screen cast if someone would like me to, or
> >>> elaborate...
> >>>
> >>> Best,
> >>>
> >>> Scott Taylor
> >>>
> >>> _______________________________________________
> >>> rspec-users mailing list
> >>> rspec-users at rubyforge.org
> >>> http://rubyforge.org/mailman/listinfo/rspec-users
> >>
> >> _______________________________________________
> >> rspec-users mailing list
> >> rspec-users at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/rspec-users
> >>
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>


More information about the rspec-users mailing list