On Wed, 19 Sep 2018 02:28:29 +0900 Doug Hellmann
wrote
> Excerpts from Clark Boylan's message of 2018-09-18 09:53:45 -0700:
> > On Tue, Sep 18, 2018, at 9:46 AM, Nate Johnston wrote:
> > > Hello python 3.6 champions,
> > >
> > > I have looked around a little, and I don't see
On Tue, Sep 18, 2018 at 09:52:50PM -0500, Matt Riedemann wrote:
> On 9/18/2018 12:28 PM, Doug Hellmann wrote:
> > What's probably missing is a version of the grenade job that allows us
> > to control that USE_PYTHON3 variable before and after the upgrade.
> >
> > I see a few different grenade jobs
On 9/18/2018 9:52 PM, Matt Riedemann wrote:
On 9/18/2018 12:28 PM, Doug Hellmann wrote:
What's probably missing is a version of the grenade job that allows us
to control that USE_PYTHON3 variable before and after the upgrade.
I see a few different grenade jobs (neutron-grenade,
neutron-grenade-
On 9/18/2018 12:28 PM, Doug Hellmann wrote:
What's probably missing is a version of the grenade job that allows us
to control that USE_PYTHON3 variable before and after the upgrade.
I see a few different grenade jobs (neutron-grenade,
neutron-grenade-multinode,
legacy-grenade-dsvm-neutron-multin
Excerpts from Clark Boylan's message of 2018-09-18 09:53:45 -0700:
> On Tue, Sep 18, 2018, at 9:46 AM, Nate Johnston wrote:
> > Hello python 3.6 champions,
> >
> > I have looked around a little, and I don't see a method for me to
> > specifically select the version of python that the tempest and g
On Tue, Sep 18, 2018, at 9:46 AM, Nate Johnston wrote:
> Hello python 3.6 champions,
>
> I have looked around a little, and I don't see a method for me to
> specifically select the version of python that the tempest and grenade
> jobs for my project (neutron) are using. I assume one of four thing
