Glad your main problem got worked out.
These search errors look to me like the system is running the search
specs but can't connect to a copy of the sphinx daemon (searchd).
Before it runs tests on sphinx, the insoshi specs code checks to see
whether a searchd process is running on your machine. If it is, it
assumes it's a test instance of sphinx and will run the tests. So,
if you're running only a development instance of searchd, the tests
will run but fail to connect to sphinx and you'll see errors like the
ones below. It's not generally a problem and doesn't interfere with
the function of the site.
This can happen if you haven't configured and started up sphinx in the
test environment (i.e. rake ultrasphinx:configure RAILS_ENV=test;
rake ultrasphinx:start RAILS_ENV=test), but you *have* started sphinx
in the development or production environment.
(I've also had this happen if, for example, I have another Rails
application on my machine that is running sphinx - insoshi's tests
will detect that copy of searchd, try to run, and fail.)
I may have to migrate the search module from ultrasphinx to
thinking_sphinx one of these days. Thinking_sphinx has a nice test
module that allows automatic starting and stopping of the correct
daemon from inside the spec files, it's very handy.
Evan Dorn,
Insoshi Maintainer
On Jan 25, 2010, at 8:12 PM, Paul Dumais wrote:
Hmm... Interesting. It all seems to work now. Also, re-running rake
spec only give 16 errors instead of the usual (> 300).
Evan Dorn, Ph.D., Owner and Lead Developer
Logical Reality Design http://LRDesign.com
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Insoshi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/insoshi?hl=en.
