On Mon, Feb 29, 2016, at 01:38 PM, Sam Yaple wrote:
> On Mon, Feb 29, 2016 at 6:42 PM, Clark Boylan
> wrote:
>
> > On Mon, Feb 29, 2016, at 09:09 AM, Steven Dake (stdake) wrote:
> > >
> > >
> > > On 2/29/16, 12:26 AM, "Andreas Jaeger" wrote:
> > > >This is
On Mon, Feb 29, 2016 at 6:42 PM, Clark Boylan wrote:
> On Mon, Feb 29, 2016, at 09:09 AM, Steven Dake (stdake) wrote:
> >
> >
> > On 2/29/16, 12:26 AM, "Andreas Jaeger" wrote:
> > >This is not needed, the CI system always rebases if you run tests. To
> >
On Mon, Feb 29, 2016, at 09:09 AM, Steven Dake (stdake) wrote:
>
>
> On 2/29/16, 12:26 AM, "Andreas Jaeger" wrote:
> >This is not needed, the CI system always rebases if you run tests. To
> >get current tests, a simple "recheck" is enough.
> >
> >Also, we test in the gate before
On 2/29/16, 12:26 AM, "Andreas Jaeger" wrote:
>On 2016-02-29 06:59, Steven Dake (stdake) wrote:
>> Hey folks,
>>
>> It should be obvious that commiters should be testing their changes, but
>> unfortunately this is not always the case. With the recent state of the
>> gate
On 2016-02-29 06:59, Steven Dake (stdake) wrote:
> Hey folks,
>
> It should be obvious that commiters should be testing their changes, but
> unfortunately this is not always the case. With the recent state of the
> gate relating to the introduction of Docker 1.10.z breaking the gate
> for 1
s)"
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [kolla] unblocking the gate
Hey folks,
It should be obvious that commiters should be testing their changes, but
unfortunately this is not always the case. With the recent state
Hey folks,
It should be obvious that commiters should be testing their changes, but
unfortunately this is not always the case. With the recent state of the gate
relating to the introduction of Docker 1.10.z breaking the gate for 1 week
followed by a keystone change upstream breaking the gate