Mel,
I think I might have fixed the test_bad_connection issue you
encountered. Errno exceptions are platform specific and I simply
loosed the test to look for ::Exception (Solr::Exception gets in the
way, requiring :: prefix, I believe).
As for test_ping - I dunno. If you cd solr; java -jar start.jar,
what do you get from going to http://localhost:8983/admin/ping ??
I get this:
<?xml-stylesheet type="text/xsl" href="ping.xsl"?>
<solr>
<ping>
</ping>
</solr>
Response::Ping checks if its ok like this:
@ok = REXML::XPath.first(@doc, './solr/ping') ? true : false
You could experiment with REXML::XPath to see if you can get this
working for you. Let us know what you discover.
Erik
On Feb 13, 2007, at 11:26 PM, Mel Riffe (JIRA) wrote:
[Patch] Get Test Solr Server working in Windows environment
-----------------------------------------------------------
Key: SOLR-160
URL: https://issues.apache.org/jira/browse/SOLR-160
Project: Solr
Issue Type: Improvement
Components: clients - ruby - flare
Environment: Windows XP Home
Reporter: Mel Riffe
Attachments: win32_functional_tests.patch,
win32_functional_tests.results
Because Windows does not support forking processes I created a
patch that uses the Win32 api to create and destroy a process to
control the test solr server.
I have attached two files: 1) the patch and 2) the results from
running 'rake test' In my environment I have two failures.
My approach was to still support the including/requiring of the
single file test/functional/test_solr_server.rb and have it further
require the platform dependent start/stop api.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
