Open Stack

On 7/11/15 6:04 AM, Robert Collins wrote:
> Wearing my upstream hat, testr is *still* intended to be used 
> differently than OpenStack is doing. Running all the tests for all 
> python versions at once in parallel is the sort of thing testr is 
> aimed at, and thats fairly fundamentally incompatible with running 
> from inside a venv. As is distributed testing across multiple 
> machines. I haven't had time to help OpenStack mature its use of testr 
> until recently, and fixing these issues that are and will have seems 
> pretty important to me. 

this is totally a peanut gallery comment, as I haven't carefully read 
this whole thread, but doesn't this mean that the use of testr *and* tox 
at the same time is fundamentally wrong?   Because tox's main purpose is 
to facilitate running tests in multiple environments (though not 
simultaneously / distributed).  If testr already does that, why are we 
using tox?  (other than the IMO fairly obvious, "it's used ubiquitously, 
is popular, and everyone knows how to use it" argument).

>> The whole argument for making testr live outside of the venv and being an
>> implicit dependency like tox is based around tracking the results between the
>> tox venvs right? If we decoupled the database and other result storage from
>> testr a bit and made that the external platform independent piece wouldn't we
>> maintain everything this thread is trying to address without having the issues
>> we're seeing now or requiring that everyone change their usage model and
>> expectations?
> Huh, no.
>
> The argument is this: a single testr knows how to run heterogeneous
> test backends which may be anywhere in the world, in any language, in
> any context. Running it from within one of those contexts is a
> seriously poor chicken-and-egg situation which doesn't make any sense.
> And the current problem with database compat due to switching out the
> python version between invocations is just the tip of the iceberg.
>
> -Rob
>
>