I'm looking into causes of this - you aren't the only one who has hit it. (https://github.com/seancribbs/ripple/issues#issue/103) So far I have been unable to reproduce it, but in the meantime, check the typical culprits:
* ulimit -n (set this in the shell where you run rake or rspec) * RAM usage (memsup may cause Riak to close) * Permissions on the relevant directories and files * Port collision - (web_port/http, pb_port, handoff_port) The test server is mostly-threadsafe but doesn't guarantee that separate threads won't collide with one another's data. Make sure your suite isn't parallelized (Spork, for example?). Sean Cribbs <[email protected]> Developer Advocate Basho Technologies, Inc. http://basho.com/ On Feb 12, 2011, at 11:43 PM, Mat Ellis wrote: > I got the wrong impression, I thought the test_server was setup by the > script. Once we setup a variant of the dev environment and pointed > test_server.rb at that things moved forward. Now we just get: > > "Broken pipe when recycling, is Riak alive?" > > > On Feb 12, 2011, at 8:31 PM, Mat Ellis wrote: > >> The specific issue we're having is that we can't get the test server to stay >> up, it seems to die after 5-6 seconds. >> >> We setup our dev environments based on the Riak Fast Track and so there was >> nothing in RIAK_ROOT/rel/riak/bin. >> >> We tried RIAK_ROOT/dev/dev1/bin and also 'make rel' in RIAK_ROOT. >> >> Any time we try any Ripple operations against the test server we get >> 'EOFError: end of file reached.' >> >> M. >> >> On Feb 12, 2011, at 8:23 PM, Sean Cribbs wrote: >> >>> The generators are there to help (assuming you have Ripple in your bundle): >>> >>> Ripple: >>> ripple >>> ripple:configuration >>> ripple:js >>> ripple:model >>> ripple:test >>> >>> The root "ripple" generator will generate configuration, js, and test. >>> >>> The "configuration" generator adds a config/ripple.yml that you use >>> normally to set up your dev and prod environments, and a hint on how to set >>> up the test env. The test server also gets its configuration from the file. >>> The only thing you really need to set is "bin_dir", which gives the >>> directory where the "riak" start script lives (depends on how you installed >>> Riak, obviously). >>> >>> The "test" generator will add the file spec/support/ripple.rb which wraps >>> the test-server up for you in a friendly package. It also inserts an "after >>> :each" block to your spec_helper.rb that wires up clearing the data for >>> you. The test server is completely independent of any stubbing or >>> additional testing frameworks you use and so it should still work for your >>> specs. Think of it like having a separate test database, with a big >>> rolled-back transaction at the end of each example. >>> >>> Sean Cribbs <[email protected]> >>> Developer Advocate >>> Basho Technologies, Inc. >>> http://basho.com/ >>> >>> On Feb 12, 2011, at 11:02 PM, Mat Ellis wrote: >>> >>>> Is there a tutorial or a walk-through available for testing with Rspec & >>>> Ripple? Currently ploughing our way through >>>> https://github.com/seancribbs/ripple/tree/41a7f741603ea186d97064ff3ef542238a078135/ripple/spec >>>> attempting to make the in memory test server work. And of course, our >>>> Rspec setup is a little different (mocha stubbing, shoulda, etc.) We'll >>>> probably get there eventually any docs or cribsheets would be helpful. >>>> >>>> TIA M. >>>> >>>> _______________________________________________ >>>> riak-users mailing list >>>> [email protected] >>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >>> >> >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
