On 05/06/17 09:43, Sean Dague wrote:
On 06/01/2017 06:09 AM, Chris Dent wrote:
It's clear from this thread and other conversations that the
management of tempest plugins is creating a multiplicity of issues
and confusions:
* Some projects are required to use plugins and some are not. This
On 06/01/2017 06:09 AM, Chris Dent wrote:
> It's clear from this thread and other conversations that the
> management of tempest plugins is creating a multiplicity of issues
> and confusions:
>
> * Some projects are required to use plugins and some are not. This
> creates classes of projects.
On Thu, 1 Jun 2017, Matthew Treinish wrote:
On Thu, Jun 01, 2017 at 11:09:56AM +0100, Chris Dent wrote:
A lot of this results, in part, from there being no single guiding
pattern and principle for how (and where) the tests are to be
managed.
It sounds like you want to write a general testing
On Thu, Jun 01, 2017 at 11:09:56AM +0100, Chris Dent wrote:
> A lot of this results, in part, from there being no single guiding
> pattern and principle for how (and where) the tests are to be
> managed.
It sounds like you want to write a general testing guide for openstack.
Have you started
Excerpts from Chris Dent's message of 2017-06-01 11:09:56 +0100:
> On Wed, 31 May 2017, Doug Hellmann wrote:
> > Yeah, it sounds like the current organization of the repo is not
> > ideal in terms of equal playing field for all of our project teams.
> > I would be fine with all of the interop
On Thu, Jun 1, 2017 at 3:39 PM, Chris Dent wrote:
> On Wed, 31 May 2017, Doug Hellmann wrote:
>
>> Yeah, it sounds like the current organization of the repo is not
>> ideal in terms of equal playing field for all of our project teams.
>> I would be fine with all of the
On Wed, 31 May 2017, Doug Hellmann wrote:
Yeah, it sounds like the current organization of the repo is not
ideal in terms of equal playing field for all of our project teams.
I would be fine with all of the interop tests being in a plugin
together, or of saying that the tempest repo should only
On Wed, May 31, 2017 at 03:22:59PM +, Jeremy Stanley wrote:
> On 2017-05-31 09:43:11 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > it's news to me that they're considering reversing course. If the
> > QA team isn't going to continue, we'll need to figure out what
> > that means and
On 2017-05-31 09:43:11 -0400 (-0400), Doug Hellmann wrote:
[...]
> it's news to me that they're considering reversing course. If the
> QA team isn't going to continue, we'll need to figure out what
> that means and potentially find another group to do it.
I wasn't there for the discussion, but it
On 31/05/17 09:43, Doug Hellmann wrote:
Excerpts from Chris Dent's message of 2017-05-31 11:22:50 +0100:
On Wed, 31 May 2017, Graham Hayes wrote:
On 30/05/17 19:09, Doug Hellmann wrote:
Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100:
Note that this goal only applies to
Excerpts from Chris Dent's message of 2017-05-31 11:22:50 +0100:
> On Wed, 31 May 2017, Graham Hayes wrote:
> > On 30/05/17 19:09, Doug Hellmann wrote:
> >> Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100:
> >>> Note that this goal only applies to tempest _plugins_. Projects
> >>>
On 31/05/17 11:22, Chris Dent wrote:
> On Wed, 31 May 2017, Graham Hayes wrote:
>> On 30/05/17 19:09, Doug Hellmann wrote:
>>> Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100:
Note that this goal only applies to tempest _plugins_. Projects
which have their tests in the
On Wed, 31 May 2017, Graham Hayes wrote:
On 30/05/17 19:09, Doug Hellmann wrote:
Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100:
Note that this goal only applies to tempest _plugins_. Projects
which have their tests in the core of tempest have nothing to do. I
wonder if it
13 matches
Mail list logo