drbspec - "no server running"

[Scott Taylor-6]

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@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Scott Taylor-6]

I've created a little 30 second screen cast to show the problem:

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@...
> http://rubyforge.org/mailman/listinfo/rspec-users

_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Aslak Hellesoy]

On 2/26/07, Scott Taylor <mailing_lists@...> wrote:
>
> I've created a little 30 second screen cast to show the problem:
>

Hey, that's a neat bug report format!

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@...
> > http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users@...
> http://rubyforge.org/mailman/listinfo/rspec-users
>

_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Scott Taylor-6]

On Feb 26, 2007, at 12:41 AM, aslak hellesoy wrote:

> On 2/26/07, Scott Taylor <mailing_lists@...> 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?

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@...
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users@...
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
> _______________________________________________
> rspec-users mailing list
> rspec-users@...
> http://rubyforge.org/mailman/listinfo/rspec-users

_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Aslak Hellesoy]

On 2/26/07, Scott Taylor <mailing_lists@...> wrote:

>
> On Feb 26, 2007, at 12:41 AM, aslak hellesoy wrote:
>
> > On 2/26/07, Scott Taylor <mailing_lists@...> 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@...
> >>> http://rubyforge.org/mailman/listinfo/rspec-users
> >>
> >> _______________________________________________
> >> rspec-users mailing list
> >> rspec-users@...
> >> http://rubyforge.org/mailman/listinfo/rspec-users
> >>
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users@...
> > http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users@...
> http://rubyforge.org/mailman/listinfo/rspec-users
>

_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Scott Taylor-6]

I removed my gem, installed the RC1...(Congratulations, btw)...

I also have the project as an externals at revision 1536.  I then  
ran ./script/generate rspec, and used the new spec --drb command.    
It worked for my models, but gave the same error for my controller spec.

I can create another screencast if you would like,

Best,

Scott



Mac OS X.4.8
ruby 1.8.5 (2006-12-25 patchlevel 12) [powerpc-darwin8.8.0]
rails: edge, revision 6239



_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Aslak Hellesoy]

On 2/26/07, Scott Taylor <mailing_lists@...> wrote:
>
> I removed my gem, installed the RC1...(Congratulations, btw)...
>
> I also have the project as an externals at revision 1536.  I then
> ran ./script/generate rspec, and used the new spec --drb command.
> It worked for my models, but gave the same error for my controller spec.
>
> I can create another screencast if you would like,
>

Some detailed steps on how to reproduce this would be more helpful for us. Code.

Aslak

> Best,
>
> Scott
>
>
>
> Mac OS X.4.8
> ruby 1.8.5 (2006-12-25 patchlevel 12) [powerpc-darwin8.8.0]
> rails: edge, revision 6239
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users@...
> http://rubyforge.org/mailman/listinfo/rspec-users
>

_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Scott Taylor-6]

Here is how I reproduced it (with a new rails project):

uninstall gem
svn co svn://rubyforge.org/var/svn/rspec/tags/REL_0_8_0_RC1/gem
gem install gem/rspec-0.8.0-RC1.gem

create new rails project
edit config/database.yml for sqlite3

rake rails:freeze:edge

./script/plugin install svn://rubyforge.org/var/svn/rspec/trunk/rspec
./script/plugin install svn://rubyforge.org/var/svn/rspec/trunk/
rspec_on_rails/vendor/plugins/rspec_on_rails

./script/generate rspec
./script/generate rspec_controller MyController
rake db:migrate (notice that I have no tables in the database,  
although I don't think that it matters...)
rake db:test:prepare
./script/rails_script/server
spec --drb spec/controllers/my_controller_controller_spec.rb

I've also created a screen cast of this, but my G4 is slow (the  
screencast is 6 minutes long)...so you might want to skip ahead of  
the downloading of edge rails, etc...

http://railsnewbie.com/files/screencasts/rspec_on_rails- 
no_server_running2.mov


I notice that if I delete all specify's and the corresponding spec's  
in the spec file, the error is no longer present.  Look at this  
screen cast (this one is only 1 minute):

http://railsnewbie.com/files/screencasts/rspec_on_rails- 
no_server_running2_part2.mov

Once again, my setup:

rails edge,
Mac OS X.4.8
ruby 1.8.5 (2006-12-25 patchlevel 12) [powerpc-darwin8.8.0]
RSpec-0.8.0 (r1497) - BDD for Ruby


Let me know if I should open a bug report.


Best,

Scott Taylor



_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Aslak Hellesoy]

On 2/26/07, Scott Taylor <mailing_lists@...> wrote:

>
> Here is how I reproduced it (with a new rails project):
>
> uninstall gem
> svn co svn://rubyforge.org/var/svn/rspec/tags/REL_0_8_0_RC1/gem
> gem install gem/rspec-0.8.0-RC1.gem
>
> create new rails project
> edit config/database.yml for sqlite3
>
> rake rails:freeze:edge
>
> ./script/plugin install svn://rubyforge.org/var/svn/rspec/trunk/rspec
> ./script/plugin install svn://rubyforge.org/var/svn/rspec/trunk/
> rspec_on_rails/vendor/plugins/rspec_on_rails
>
> ./script/generate rspec
> ./script/generate rspec_controller MyController
> rake db:migrate (notice that I have no tables in the database,
> although I don't think that it matters...)
> rake db:test:prepare
> ./script/rails_script/server
> spec --drb spec/controllers/my_controller_controller_spec.rb
>
> I've also created a screen cast of this, but my G4 is slow (the
> screencast is 6 minutes long)...so you might want to skip ahead of
> the downloading of edge rails, etc...
>
> http://railsnewbie.com/files/screencasts/rspec_on_rails-
> no_server_running2.mov
>
>
> I notice that if I delete all specify's and the corresponding spec's
> in the spec file, the error is no longer present.  Look at this
> screen cast (this one is only 1 minute):
>
> http://railsnewbie.com/files/screencasts/rspec_on_rails-
> no_server_running2_part2.mov
>
> Once again, my setup:
>
> rails edge,
> Mac OS X.4.8
> ruby 1.8.5 (2006-12-25 patchlevel 12) [powerpc-darwin8.8.0]
> RSpec-0.8.0 (r1497) - BDD for Ruby
>
>
> Let me know if I should open a bug report.
>

Please do, or we'll forget.

Aslak

>
> Best,
>
> Scott Taylor
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users@...
> http://rubyforge.org/mailman/listinfo/rspec-users
>

_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Scott Taylor-6]

The latest bug - the one that I've just put into the tracker - is  
halting all work that I'm doing on this rails project.  I would like  
to contribute back to the community, and fix the bug for myself.  Any  
suggestions on how to do this?  Maybe some suggestions for how to  
debug a code base which you are unfamiliar with?

One thing I would like to do is run all of the specs in the rspec  
library to see if they are passing. - the ones that fail will  
probably point to the culprit.  How can I run all of the specs under  
one directory, if the specs are under subdirectories?  This maybe  
more of a unix question then an rspec one...


Thanks for the help,

Scott Taylor

_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Jerry West]

> One thing I would like to do is run all of the specs in the rspec  
> library to see if they are passing. - the ones that fail will  
> probably point to the culprit.  How can I run all of the specs under  
> one directory, if the specs are under subdirectories?  This maybe  
> more of a unix question then an rspec one...

Well, for the 0.7.5.1 plugin

cd $RAILSDIR; spec -cfs vendor/plugins/rspec_on_rails/spec/


I imagine the filesystem layout is the same for 0.8/trunk(?).

Ironically, you can't run many of the 0.7.5.1 specs under 0.7.5.1 as
they use the latest 'should' syntax available only with 0.8RC1/trunk.

Hope this helps,
   Jerry

_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Aslak Hellesoy]

On 2/27/07, Scott Taylor <mailing_lists@...> wrote:

>
> The latest bug - the one that I've just put into the tracker - is
> halting all work that I'm doing on this rails project.  I would like
> to contribute back to the community, and fix the bug for myself.  Any
> suggestions on how to do this?  Maybe some suggestions for how to
> debug a code base which you are unfamiliar with?
>
> One thing I would like to do is run all of the specs in the rspec
> library to see if they are passing. - the ones that fail will
> probably point to the culprit.  How can I run all of the specs under
> one directory, if the specs are under subdirectories?  This maybe
> more of a unix question then an rspec one...
>

Try this:

spec --help

The first line of the help tells you that you can pass a directory to
the spec command:

spec some/dir

If you want to run RSpec's own suite of specs, check out the code with
svn and read the README.

HTH,
Aslak

>
> Thanks for the help,
>
> Scott Taylor
>
> _______________________________________________
> rspec-users mailing list
> rspec-users@...
> http://rubyforge.org/mailman/listinfo/rspec-users
>

_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[Aslak Hellesoy]

On 2/27/07, Jerry West <jerry.west@...> wrote:

>
> > One thing I would like to do is run all of the specs in the rspec
> > library to see if they are passing. - the ones that fail will
> > probably point to the culprit.  How can I run all of the specs under
> > one directory, if the specs are under subdirectories?  This maybe
> > more of a unix question then an rspec one...
>
> Well, for the 0.7.5.1 plugin
>
> cd $RAILSDIR; spec -cfs vendor/plugins/rspec_on_rails/spec/
>
>
> I imagine the filesystem layout is the same for 0.8/trunk(?).
>
> Ironically, you can't run many of the 0.7.5.1 specs under 0.7.5.1 as
> they use the latest 'should' syntax available only with 0.8RC1/trunk.
>

You can, but instead of saying "spec" (which will run your
gem-installed spec) you have to say "bin/spec" (assuming you're
standing in the root directory of rspec core)

Aslak

> Hope this helps,
>    Jerry
>
> _______________________________________________
> rspec-users mailing list
> rspec-users@...
> http://rubyforge.org/mailman/listinfo/rspec-users
>
_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[David Chelimsky-2]

On 2/27/07, Jerry West <jerry.west@...> wrote:

>
> > One thing I would like to do is run all of the specs in the rspec
> > library to see if they are passing. - the ones that fail will
> > probably point to the culprit.  How can I run all of the specs under
> > one directory, if the specs are under subdirectories?  This maybe
> > more of a unix question then an rspec one...
>
> Well, for the 0.7.5.1 plugin
>
> cd $RAILSDIR; spec -cfs vendor/plugins/rspec_on_rails/spec/
>
>
> I imagine the filesystem layout is the same for 0.8/trunk(?).
>
> Ironically, you can't run many of the 0.7.5.1 specs under 0.7.5.1 as
> they use the latest 'should' syntax available only with 0.8RC1/trunk.

Hi Jerry,

Thanks for your interest in contributing.
http://rspec.rubyforge.org/contribute.html might provide a little more
insight.

We are aware of the problems running Spec::Rails' own specs outside of
the project in which it lives in trunk. The problem we ran into is
that there are things that are supposed to be configurable which turn
out not to be, like where Rails looks for controllers, etc. This is a
problem we plan to address before 1.0, but it is not the highest
priority right now.

That said, if you're going to work on rspec, the best thing to do is
to submit a patch against the trunk. Check out the entire trunk and do
this from the project root:

rake install_dependencies
cd rspec_on_rails
rake rspec:pre_commit

The last command runs rspec against 1.1.6, 1.2.1 and 1.2.2. To run it
against edge as well, you need to run the following, all on one line.

RSPEC_RAILS_VERSION=edge rake spec:all

You can also tweak at rspec_on_rails/Mutlirails.rake if you want to
include edge in rake:pre_commit.

Please feel free to ask if you run into any problems at all. There are
several people on this list who have contributed to rspec and can help
if none of the core team are available to respond right away.

Cheers,
David








>
> Hope this helps,
>    Jerry
>
> _______________________________________________
> rspec-users mailing list
> rspec-users@...
> http://rubyforge.org/mailman/listinfo/rspec-users
>
_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[David Chelimsky-2]

On 2/27/07, David Chelimsky <dchelimsky@...> wrote:

> On 2/27/07, Jerry West <jerry.west@...> wrote:
> >
> > > One thing I would like to do is run all of the specs in the rspec
> > > library to see if they are passing. - the ones that fail will
> > > probably point to the culprit.  How can I run all of the specs under
> > > one directory, if the specs are under subdirectories?  This maybe
> > > more of a unix question then an rspec one...
> >
> > Well, for the 0.7.5.1 plugin
> >
> > cd $RAILSDIR; spec -cfs vendor/plugins/rspec_on_rails/spec/
> >
> >
> > I imagine the filesystem layout is the same for 0.8/trunk(?).
> >
> > Ironically, you can't run many of the 0.7.5.1 specs under 0.7.5.1 as
> > they use the latest 'should' syntax available only with 0.8RC1/trunk.

Actually, expression matchers for #should were introduced quietly in
0.7.5, so this is not quite correct. If you check out the entire
0.7.5.1 project and have no other instances of rspec installed you'll
be able to run the specs.

>
> Hi Jerry,
>
> Thanks for your interest in contributing.
> http://rspec.rubyforge.org/contribute.html might provide a little more
> insight.
>
> We are aware of the problems running Spec::Rails' own specs outside of
> the project in which it lives in trunk. The problem we ran into is
> that there are things that are supposed to be configurable which turn
> out not to be, like where Rails looks for controllers, etc. This is a
> problem we plan to address before 1.0, but it is not the highest
> priority right now.
>
> That said, if you're going to work on rspec, the best thing to do is
> to submit a patch against the trunk. Check out the entire trunk and do
> this from the project root:
>
> rake install_dependencies
> cd rspec_on_rails
> rake rspec:pre_commit
>
> The last command runs rspec against 1.1.6, 1.2.1 and 1.2.2. To run it
> against edge as well, you need to run the following, all on one line.
>
> RSPEC_RAILS_VERSION=edge rake spec:all
>
> You can also tweak at rspec_on_rails/Mutlirails.rake if you want to
> include edge in rake:pre_commit.
>
> Please feel free to ask if you run into any problems at all. There are
> several people on this list who have contributed to rspec and can help
> if none of the core team are available to respond right away.
>
> Cheers,
> David
>
>
>
>
>
>
>
>
> >
> > Hope this helps,
> >    Jerry
> >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users@...
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
>

_______________________________________________
rspec-users mailing list
rspec-users@...
http://rubyforge.org/mailman/listinfo/rspec-users

[gmcinnes]

Hi:  I can't find the bug report.  Maybe you didn't make it yet.

I solved this by adding my machine name to /etc/localhosts - i.e. my computer is called morgan, and I added:


127.0.0.1                      morgan


to that file.


It seems os x  fancypants name lookup system doesn't resolve the machine name when making a gethostbyaddr(host)[0] call unless the machine name is in localhost.  Seems to be a drb problem though.

aslak hellesoy wrote:

On 2/26/07, Scott Taylor <[e-mail]> wrote:
>
> On Feb 26, 2007, at 12:41 AM, aslak hellesoy wrote:
>
> > On 2/26/07, Scott Taylor <[e-mail]> 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
> >>> [e-mail]
> >>> http://rubyforge.org/mailman/listinfo/rspec-users
> >>
> >> _______________________________________________
> >> rspec-users mailing list
> >> [e-mail]
> >> http://rubyforge.org/mailman/listinfo/rspec-users
> >>
> > _______________________________________________
> > rspec-users mailing list
> > [e-mail]
> > http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> [e-mail]
> http://rubyforge.org/mailman/listinfo/rspec-users
>
_______________________________________________
rspec-users mailing list
[e-mail]
http://rubyforge.org/mailman/listinfo/rspec-users