Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

no, i’m not. i just figured i should target python 3.6 if i was doing this work in the first place. the current Ubuntu LTS was pulling in a pretty old version. any concerns with using 3.6? > On Jan 3, 2018, at 1:51 AM, Stefan Podkowinski wrote: > > The latest updates to your

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

The latest updates to your branch fixed the logging issue, thanks! Tests now seem to execute fine locally using pytest. I was looking at the dockerfile and noticed that you explicitly use python 3.6 there. Are you aware of any issues with older python3 versions, e.g. 3.5? Do I have to use 3.6 as

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

I reproduced the NOTSET log issue locally... got a fix.. i'll push a commit up in a moment. > On Jan 2, 2018, at 11:24 AM, Michael Kjellman > wrote: > > Comments Inline: Thanks for giving this a go!! > >> On Jan 2, 2018, at 6:10 AM, Stefan Podkowinski

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

Comments Inline: Thanks for giving this a go!! > On Jan 2, 2018, at 6:10 AM, Stefan Podkowinski wrote: > > I was giving this a try today with some mixed results. First of all, > running pytest locally would fail with an "ccmlib.common.ArgumentError: > Unknown log level NOTSET"

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

I was giving this a try today with some mixed results. First of all, running pytest locally would fail with an "ccmlib.common.ArgumentError: Unknown log level NOTSET" error for each test. Although I created a new virtualenv for that as described in the readme (thanks for updating!) and use both of

[Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

I just created https://issues.apache.org/jira/browse/CASSANDRA-14134 which includes tons of details (and a patch available for review) with my efforts to migrate dtests from nosetest to pytest (which ultimately ended up also including porting the ode from python 2.7 to python 3). I'd love if