On 13 July 2015 at 06:19, Mike Bayer wrote:
>
>
> 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
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 wi
On 11 July 2015 at 22:04, Robert Collins wrote:
> On 11 July 2015 at 12:38, Matthew Treinish wrote:
>> 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 th
On 11 July 2015 at 12:38, Matthew Treinish wrote:
> On Sat, Jul 11, 2015 at 11:35:16AM +1200, Robert Collins wrote:
>> On 9 July 2015 at 10:52, Jeremy Stanley wrote:
>> > On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote:
>> >> So - I'm looking to:
>> >>
>> >> A) have a discussion and id
On 11 July 2015 at 15:54, Ian Cordasco wrote:
> On 7/10/15, 18:34, "Monty Taylor" wrote:
>
>>On 07/10/2015 07:19 PM, Robert Collins wrote:
>>> On 10 July 2015 at 01:59, Morgan Fainberg
>>>wrote:
Or a database per python major version (or at least gracefully handle
the incompatibility).
On 7/10/15, 18:34, "Monty Taylor" wrote:
>On 07/10/2015 07:19 PM, Robert Collins wrote:
>> On 10 July 2015 at 01:59, Morgan Fainberg
>>wrote:
>>> Or a database per python major version (or at least gracefully handle
>>>the incompatibility).
>>
>> So that would partition the data, and the whole
On Sat, Jul 11, 2015 at 11:35:16AM +1200, Robert Collins wrote:
> On 9 July 2015 at 10:52, Jeremy Stanley wrote:
> > On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote:
> >> So - I'm looking to:
> >>
> >> A) have a discussion and identify any issues with moving testr out of
> >> the venvs.
On Thu, Jul 09, 2015 at 06:59:44AM -0700, Morgan Fainberg wrote:
> Or a database per python major version (or at least gracefully handle the
> incompatibility).
>
> --Morgan
>
> Sent via mobile
>
> > On Jul 9, 2015, at 06:43, Doug Hellmann wrote:
> >
> > Excerpts from Robert Collins's message
On 11 July 2015 at 11:34, Monty Taylor wrote:
> On 07/10/2015 07:19 PM, Robert Collins wrote:
>> On 10 July 2015 at 01:59, Morgan Fainberg wrote:
>>> Or a database per python major version (or at least gracefully handle the
>>> incompatibility).
>>
>> So that would partition the data, and the wh
On 9 July 2015 at 10:52, Jeremy Stanley wrote:
> On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote:
>> So - I'm looking to:
>>
>> A) have a discussion and identify any issues with moving testr out of
>> the venvs. (Note: this doesn't mean stop using it, just removing it
>> from test-requi
On 9 July 2015 at 18:34, Flavio Percoco wrote:
> On 08/07/15 22:52 +, Jeremy Stanley wrote:
>>
>> On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote:
>>>
>>> So - I'm looking to:
>>>
>>> A) have a discussion and identify any issues with moving testr out of
>>> the venvs. (Note: this do
On 07/10/2015 07:19 PM, Robert Collins wrote:
> On 10 July 2015 at 01:59, Morgan Fainberg wrote:
>> Or a database per python major version (or at least gracefully handle the
>> incompatibility).
>
> So that would partition the data, and the whole point of test
> *repository* is that it builds a
On 10 July 2015 at 01:59, Morgan Fainberg wrote:
> Or a database per python major version (or at least gracefully handle the
> incompatibility).
So that would partition the data, and the whole point of test
*repository* is that it builds a database across all your tests to
answer useful question
Or a database per python major version (or at least gracefully handle the
incompatibility).
--Morgan
Sent via mobile
> On Jul 9, 2015, at 06:43, Doug Hellmann wrote:
>
> Excerpts from Robert Collins's message of 2015-07-09 10:37:17 +1200:
>> I don't remember if this has previously been discu
Excerpts from Robert Collins's message of 2015-07-09 10:37:17 +1200:
> I don't remember if this has previously been discussed, but as our
> Python3 readiness increases folk are going to feel pain from testr due
> to a silly Python 2/3 incompatibility around dbm files.
>
> https://bugs.launchpad.ne
On 7/9/15, 01:34, "Flavio Percoco" wrote:
>On 08/07/15 22:52 +, Jeremy Stanley wrote:
>>On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote:
>>> So - I'm looking to:
>>>
>>> A) have a discussion and identify any issues with moving testr out of
>>> the venvs. (Note: this doesn't mean
On 08/07/15 22:52 +, Jeremy Stanley wrote:
On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote:
So - I'm looking to:
A) have a discussion and identify any issues with moving testr out of
the venvs. (Note: this doesn't mean stop using it, just removing it
from test-requirements.txt, i
On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote:
> So - I'm looking to:
>
> A) have a discussion and identify any issues with moving testr out of
> the venvs. (Note: this doesn't mean stop using it, just removing it
> from test-requirements.txt, in the same way that tox isn't in
> test-
I don't remember if this has previously been discussed, but as our
Python3 readiness increases folk are going to feel pain from testr due
to a silly Python 2/3 incompatibility around dbm files.
https://bugs.launchpad.net/testrepository/+bug/1212909
OpenStack (alone in the universe as far as I can
19 matches
Mail list logo
