[opensuse-buildservice] Problem with testing (ThinkingSphinx)
Hi, since a few days I get some error messages while doing testing Steps to reproduce * Clone git * bring up a Vagrant machine ("vagrant up") * ssh to vagrant machine "vagrant ssh" * start tests "make -C /vagrant/src/api test" ** this simply executes script/api_test_in_spec.sh This leads to an error with ThinkingSphinx (tries to connect to 127.0.0.1) (for detailed errors see the following link) http://pastebin.com/yjzcfYmd Could somebody shade some light on me ? What I'am doing wrong, or give me some feedback (whether it works or not on your side ?) THX M0ses -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hey, On 18.01.2016 13:53, Frank Schreiner wrote:
* Clone git * bring up a Vagrant machine ("vagrant up") * ssh to vagrant machine "vagrant ssh" * start tests "make -C /vagrant/src/api test" ** this simply executes script/api_test_in_spec.sh
This leads to an error with ThinkingSphinx (tries to connect to 127.0.0.1) (for detailed errors see the following link)
Could somebody shade some light on me ? What I'am doing wrong, or give me some feedback (whether it works or not on your side ?)
As far as I know we don't start TS. rake ts:start would do it. Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 19 January 2016, 11:48:33 wrote Henne Vogelsang:
Hey,
On 18.01.2016 13:53, Frank Schreiner wrote:
* Clone git * bring up a Vagrant machine ("vagrant up") * ssh to vagrant machine "vagrant ssh" * start tests "make -C /vagrant/src/api test" ** this simply executes script/api_test_in_spec.sh
This leads to an error with ThinkingSphinx (tries to connect to 127.0.0.1) (for detailed errors see the following link)
Could somebody shade some light on me ? What I'am doing wrong, or give me some feedback (whether it works or not on your side ?)
As far as I know we don't start TS.
we do so, (or better the thinking-sphinx gem does so). This is also the stuff which hangs from time to time, esp in internal build service. (either during indexing or daemon start)
rake ts:start
would do it.
Henne
-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Dienstag, den 19.01.2016, 13:36 +0100 schrieb Adrian Schröter:
On Tuesday 19 January 2016, 11:48:33 wrote Henne Vogelsang:
Hey,
On 18.01.2016 13:53, Frank Schreiner wrote:
* Clone git * bring up a Vagrant machine ("vagrant up") * ssh to vagrant machine "vagrant ssh" * start tests "make -C /vagrant/src/api test" ** this simply executes script/api_test_in_spec.sh
This leads to an error with ThinkingSphinx (tries to connect to 127.0.0.1) (for detailed errors see the following link)
Could somebody shade some light on me ? What I'am doing wrong, or give me some feedback (whether it works or not on your side ?)
As far as I know we don't start TS.
we do so, (or better the thinking-sphinx gem does so).
This is also the stuff which hangs from time to time, esp in internal build service. (either during indexing or daemon start)
in obs it works fine, but I run the tests in a vagrant machine and it fails every time.
rake ts:start
did not help - Im wondering if maybe a instance of searchd is already started in the vagrant vm. Will check this and write about results. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Adrian Schröter -
Frank Schreiner -
Henne Vogelsang