Re: [PROPOSAL] Migrate to pytest from nosetests for dtests

2017-11-29 Thread kurt greaves
me i > see fail 1 in 10 runs. > > > > the net of it all though is this makes people not trust dtests because > it randomly hangs and shows tests with “failures” that actually succeeded. > > > > i’m not a huge fan of just blindly upgrading to fix a problem but in > th

Re: [PROPOSAL] Migrate to pytest from nosetests for dtests

2017-11-29 Thread Michael Kjellman
se it > randomly hangs and shows tests with “failures” that actually succeeded. > > i’m not a huge fan of just blindly upgrading to fix a problem but in this > case I found that there is quite a lot of mistrust and dislike for nosetests > in the python community with most project

Re: [PROPOSAL] Migrate to pytest from nosetests for dtests

2017-11-29 Thread Michael Kjellman
a problem but in this case I found that there is quite a lot of mistrust and dislike for nosetests in the python community with most projects already moving to pytest. and if it is some complicated set of interactions between threads we use in the tests and how nose works do we really want to

Re: [PROPOSAL] Migrate to pytest from nosetests for dtests

2017-11-29 Thread Philip Thompson
; I'd like to propose we move from nosetest to pytest for the dtests. It > looks like nosetests is basically abandoned, the python community doesn't > like it, it hasn't been updated since 2015, and pytest even has nosetests > support which would help us greatly during migrat

Re: [PROPOSAL] Migrate to pytest from nosetests for dtests

2017-11-28 Thread Jon Haddad
+1 I stopped using nose a long time ago in favor of py.test. It’s a significant improvement. > On Nov 28, 2017, at 10:49 AM, Michael Kjellman wrote: > > I'd like to propose we move from nosetest to pytest for the dtests. It looks > like nosetests is basically abandoned, the

[PROPOSAL] Migrate to pytest from nosetests for dtests

2017-11-28 Thread Michael Kjellman
I'd like to propose we move from nosetest to pytest for the dtests. It looks like nosetests is basically abandoned, the python community doesn't like it, it hasn't been updated since 2015, and pytest even has nosetests support which would help us greatly during mi

Re: nosetests

2012-04-14 Thread Pavel Yaskevich
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 t

Re: nosetests

2012-04-14 Thread Mark Dewey
-- On Sat, Apr 14, 2012 at 2:33 PM, Brandon Williams wrote: > 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 >> >

Re: nosetests

2012-04-14 Thread Brandon Williams
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 >

Re: nosetests

2012-04-14 Thread Jonathan Ellis
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 p

Re: nosetests

2012-04-14 Thread aaron morton
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 -

Re: nosetests

2012-04-14 Thread Mark Dewey
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", li

nosetests

2012-04-14 Thread Mark Dewey
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

Re: No module named cql - nosetests test/system/

2011-06-27 Thread Jonathan Ellis
;/Users/joestein/source-apache-cassandra/cassandra-trunk/test/system/test_cql.py", >> > line 26, in >> >    import cql >> > ImportError: No module named cql >> > >> > I followed the steps >> > >> > new-host-3:source-apache-cassandr

Re: No module named cql - nosetests test/system/

2011-06-27 Thread Joseph Stein
(part_fqname, fh, filename, desc) > > File > > > "/Users/joestein/source-apache-cassandra/cassandra-trunk/test/system/test_cql.py", > > line 26, in > >import cql > > ImportError: No module named cql > > > > I followed the steps > > >

Re: No module named cql - nosetests test/system/

2011-06-27 Thread Jonathan Ellis
assandra/cassandra-trunk/test/system/test_cql.py", > line 26, in >    import cql > ImportError: No module named cql > > I followed the steps > > new-host-3:source-apache-cassandra joestein$ sudo easy_install nose > Password: > Searching for nose > Best match: nose 0.

No module named cql - nosetests test/system/

2011-06-27 Thread Joseph Stein
st/system/test_cql.py", line 26, in import cql ImportError: No module named cql I followed the steps new-host-3:source-apache-cassandra joestein$ sudo easy_install nose Password: Searching for nose Best match: nose 0.11.4 Processing nose-0.11.4-py2.6.egg nose 0.11.4 is already the active version