On 8/19/2016 9:42 AM, Mike Bayer wrote:
On 08/18/2016 11:00 AM, Matt Riedemann wrote:
It's that time of year again to talk about killing this job, at least
from the integrated gate (move it to experimental for people that care
about postgresql, or make it gating on a smaller subset of projects
On 08/18/2016 11:00 AM, Matt Riedemann wrote:
It's that time of year again to talk about killing this job, at least
from the integrated gate (move it to experimental for people that care
about postgresql, or make it gating on a smaller subset of projects like
oslo.db).
Running a full tempest
On 8/18/2016 3:44 PM, Michael Still wrote:
On Fri, Aug 19, 2016 at 1:00 AM, Matt Riedemann
mailto:mrie...@linux.vnet.ibm.com>> wrote:
It's that time of year again to talk about killing this job, at
least from the integrated gate (move it to experimental for people
that care about pos
On 08/18/2016 02:22 PM, Sean Dague wrote:
> On 08/18/2016 11:00 AM, Matt Riedemann wrote:
>> It's that time of year again to talk about killing this job, at least
>> from the integrated gate (move it to experimental for people that care
>> about postgresql, or make it gating on a smaller subset of
On Fri, Aug 19, 2016 at 1:00 AM, Matt Riedemann
wrote:
> It's that time of year again to talk about killing this job, at least from
> the integrated gate (move it to experimental for people that care about
> postgresql, or make it gating on a smaller subset of projects like oslo.db).
>
> The post
On 08/18/2016 03:31 PM, Matthew Thode wrote:
> On 08/18/2016 01:50 PM, Matt Riedemann wrote:
>> On 8/18/2016 1:18 PM, Matthew Thode wrote:
>>> Perhaps a better option would be to get oslo.db to run cross-project
>>> checks like we do in requirements. That way the right team is covering
>>> the usa
On 08/18/2016 01:50 PM, Matt Riedemann wrote:
> On 8/18/2016 1:18 PM, Matthew Thode wrote:
>> Perhaps a better option would be to get oslo.db to run cross-project
>> checks like we do in requirements. That way the right team is covering
>> the usage of postgres and we still have coverage while sti
On 8/18/2016 1:18 PM, Matthew Thode wrote:
Perhaps a better option would be to get oslo.db to run cross-project
checks like we do in requirements. That way the right team is covering
the usage of postgres and we still have coverage while still lowering
gate load for most projects.
___
Excerpts from Matthew Thode's message of 2016-08-18 13:18:05 -0500:
> On 08/18/2016 10:00 AM, Matt Riedemann wrote:
> > It's that time of year again to talk about killing this job, at least
> > from the integrated gate (move it to experimental for people that care
> > about postgresql, or make it g
On 8/18/2016 12:14 PM, Matthew Treinish wrote:
On Thu, Aug 18, 2016 at 11:33:59AM -0500, Matthew Thode wrote:
On 08/18/2016 10:00 AM, Matt Riedemann wrote:
It's that time of year again to talk about killing this job, at least
from the integrated gate (move it to experimental for people that car
On 08/18/2016 11:00 AM, Matt Riedemann wrote:
> It's that time of year again to talk about killing this job, at least
> from the integrated gate (move it to experimental for people that care
> about postgresql, or make it gating on a smaller subset of projects like
> oslo.db).
>
> The postgresql j
On 08/18/2016 10:00 AM, Matt Riedemann wrote:
> It's that time of year again to talk about killing this job, at least
> from the integrated gate (move it to experimental for people that care
> about postgresql, or make it gating on a smaller subset of projects like
> oslo.db).
>
> The postgresql j
On Thu, Aug 18, 2016 at 11:33:59AM -0500, Matthew Thode wrote:
> On 08/18/2016 10:00 AM, Matt Riedemann wrote:
> > It's that time of year again to talk about killing this job, at least
> > from the integrated gate (move it to experimental for people that care
> > about postgresql, or make it gating
On 08/18/2016 10:00 AM, Matt Riedemann wrote:
> It's that time of year again to talk about killing this job, at least
> from the integrated gate (move it to experimental for people that care
> about postgresql, or make it gating on a smaller subset of projects like
> oslo.db).
>
> The postgresql j
It's that time of year again to talk about killing this job, at least
from the integrated gate (move it to experimental for people that care
about postgresql, or make it gating on a smaller subset of projects like
oslo.db).
The postgresql job used to have three interesting things about it:
1.
15 matches
Mail list logo
