That happens sometimes when tests fail unexpectedly, you can delete
/home/mildewey/Projects/cassandra/system_test.pid and start nosetests again.
On Sunday 15 April 2012 at 01:35, Mark Dewey wrote:
> With the =ve I got 92 copies of this (one for each test):
>
> ==
With the =ve I got 92 copies of this (one for each test):
==
ERROR: system.test_thrift_server.TestTruncate.test_truncate
--
Traceback (most recent call last):
F
Try nosetests -ve to see which one is failing and exit on the first error.
On Apr 14, 2012 1:34 PM, "Mark Dewey" wrote:
> I thought I followed the instructions to set up the nose tests, but when I
> run them all they do is (slowly) print out ".E" and then hang. Any clues?
>
> Mark
>
nosetests manages starting and tearing down its own local Cassandra
instance; if you start one manually it will likely conflict.
On Sat, Apr 14, 2012 at 1:44 PM, aaron morton wrote:
> Looks like it's hanging while talking to the cluster. Ensure cassandra is
> running and on default ports.
>
> I
Looks like it's hanging while talking to the cluster. Ensure cassandra is
running and on default ports.
I also run nosetests with -vdx for verbose, detailed errors and stop of first
fail (http://readthedocs.org/docs/nose/en/latest/usage.html#extended-usage)
Cheers
-
Aaron Mor
PS I got the following trace when I aborted.
Traceback (most recent call last):
File "/usr/bin/nosetests", line 9, in
load_entry_point('nose==0.11.4', 'console_scripts', 'nosetests')()
File "/usr/lib/pymodules/python2.7/nose/core.py", line 117, in __init__
**extra_args)
File "/usr/l
I thought I followed the instructions to set up the nose tests, but when I
run them all they do is (slowly) print out ".E" and then hang. Any clues?
Mark
