Re: [openstack-dev] New Python35 Jobs coming

[Andreas Jaeger]

On 07/05/2016 02:52 PM, Andreas Jaeger wrote:
> [...]
> The change has merged and the python35 non-voting tests are run as part
> of new changes now.
> 
> The database setup for the python35-db variant is not working yet, and
> needs adjustment on the infra side.


The python35-db jobs are working now as well.

Happy Python35 testing,
Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] New Python35 Jobs coming

[Andreas Jaeger]

On 2016-07-01 21:51, Clark Boylan wrote:
> The infra team is working on taking advantage of the new Ubuntu Xenial
> release including running unittests on python35. The current plan is to
> get https://review.openstack.org/#/c/336272/ merged next Tuesday (July
> 5, 2016). This will add non voting python35 tests restricted to >=
> master/Newton on all projects that had python34 testing.
> 
> The expectation is that in many cases python35 tests will just work if
> python34 testing was also working. If this is the case for your project
> you can propose a change to openstack-infra/project-config to make these
> jobs voting against your project. You should only need to edit
> jenkins/jobs/projects.yaml and zuul/layout.yaml and remove the '-nv'
> portion of the python35 jobs to do this.
> 
> We do however expect that there will be a large group of failed tests
> too. If your project has a specific tox.ini py34 target to restrict
> python3 testing to a specific list of tests you will need to add a tox
> target for py35 that does the same thing as the py34 target. We have
> also seen bug reports against some projects whose tests rely on stable
> error messages from Python itself which isn't always the case across
> version changes so these tests will need to be updated as well.
> 
> Note this change will not add python35 jobs for cases where projects
> have special tox targets. This is restricted just to the default py35
> unittesting.
> 
> As always let us know if you questions,
> Clark

The change has merged and the python35 non-voting tests are run as part
of new changes now.

The database setup for the python35-db variant is not working yet, and
needs adjustment on the infra side.

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] New Python35 Jobs coming

[Victor Stinner]

Le 04/07/2016 à 07:59, Denis Makogon a écrit :

Then let it run for a day or two in our CI, discuss with neutron team,
and send a patch for project-config to change the setup,

Can confirm that nova, glance, cinder, heat clients are py35 compatible.


tox.ini of Nova, Swift and Trove need to be modified to copy/paste the 
whitelist of tests running on Python 3. Fix for Nova:


   https://review.openstack.org/#/c/336432/

Victor

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] New Python35 Jobs coming

[Denis Makogon]

2016-07-04 8:18 GMT+03:00 Andreas Jaeger :

> On 07/03/2016 09:26 PM, Henry Gessau wrote:
> > Clark Boylan  wrote:
> >> The infra team is working on taking advantage of the new Ubuntu Xenial
> >> release including running unittests on python35. The current plan is to
> >> get https://review.openstack.org/#/c/336272/ merged next Tuesday (July
> >> 5, 2016). This will add non voting python35 tests restricted to >=
> >> master/Newton on all projects that had python34 testing.
> >>
> >> The expectation is that in many cases python35 tests will just work if
> >> python34 testing was also working. If this is the case for your project
> >> you can propose a change to openstack-infra/project-config to make these
> >> jobs voting against your project. You should only need to edit
> >> jenkins/jobs/projects.yaml and zuul/layout.yaml and remove the '-nv'
> >> portion of the python35 jobs to do this.
> >>
> >> We do however expect that there will be a large group of failed tests
> >> too. If your project has a specific tox.ini py34 target to restrict
> >> python3 testing to a specific list of tests you will need to add a tox
> >> target for py35 that does the same thing as the py34 target. We have
> >> also seen bug reports against some projects whose tests rely on stable
> >> error messages from Python itself which isn't always the case across
> >> version changes so these tests will need to be updated as well.
> >>
> >> Note this change will not add python35 jobs for cases where projects
> >> have special tox targets. This is restricted just to the default py35
> >> unittesting.
> >>
> >> As always let us know if you questions,
> >> Clark
> >
> > How soon can projects replace py34 with py35?
>
> As soon as you think your project is ready, you can replace py34 with
> py35 for master.
>
> >
> > I tried py35 for neutron locally, and it ran without errors.
>
> Then let it run for a day or two in our CI, discuss with neutron team,
> and send a patch for project-config to change the setup,
>
>
Can confirm that nova, glance, cinder, heat clients are py35 compatible.


> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>HRB 21284 (AG Nürnberg)
> GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] New Python35 Jobs coming

[Andreas Jaeger]

On 07/03/2016 09:26 PM, Henry Gessau wrote:
> Clark Boylan  wrote:
>> The infra team is working on taking advantage of the new Ubuntu Xenial
>> release including running unittests on python35. The current plan is to
>> get https://review.openstack.org/#/c/336272/ merged next Tuesday (July
>> 5, 2016). This will add non voting python35 tests restricted to >=
>> master/Newton on all projects that had python34 testing.
>>
>> The expectation is that in many cases python35 tests will just work if
>> python34 testing was also working. If this is the case for your project
>> you can propose a change to openstack-infra/project-config to make these
>> jobs voting against your project. You should only need to edit
>> jenkins/jobs/projects.yaml and zuul/layout.yaml and remove the '-nv'
>> portion of the python35 jobs to do this.
>>
>> We do however expect that there will be a large group of failed tests
>> too. If your project has a specific tox.ini py34 target to restrict
>> python3 testing to a specific list of tests you will need to add a tox
>> target for py35 that does the same thing as the py34 target. We have
>> also seen bug reports against some projects whose tests rely on stable
>> error messages from Python itself which isn't always the case across
>> version changes so these tests will need to be updated as well.
>>
>> Note this change will not add python35 jobs for cases where projects
>> have special tox targets. This is restricted just to the default py35
>> unittesting.
>>
>> As always let us know if you questions,
>> Clark
> 
> How soon can projects replace py34 with py35?

As soon as you think your project is ready, you can replace py34 with
py35 for master.

> 
> I tried py35 for neutron locally, and it ran without errors.

Then let it run for a day or two in our CI, discuss with neutron team,
and send a patch for project-config to change the setup,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] New Python35 Jobs coming

[Clint Byrum]

Excerpts from Henry Gessau's message of 2016-07-03 15:26:23 -0400:
> Clark Boylan  wrote:
> > The infra team is working on taking advantage of the new Ubuntu Xenial
> > release including running unittests on python35. The current plan is to
> > get https://review.openstack.org/#/c/336272/ merged next Tuesday (July
> > 5, 2016). This will add non voting python35 tests restricted to >=
> > master/Newton on all projects that had python34 testing.
> > 
> > The expectation is that in many cases python35 tests will just work if
> > python34 testing was also working. If this is the case for your project
> > you can propose a change to openstack-infra/project-config to make these
> > jobs voting against your project. You should only need to edit
> > jenkins/jobs/projects.yaml and zuul/layout.yaml and remove the '-nv'
> > portion of the python35 jobs to do this.
> > 
> > We do however expect that there will be a large group of failed tests
> > too. If your project has a specific tox.ini py34 target to restrict
> > python3 testing to a specific list of tests you will need to add a tox
> > target for py35 that does the same thing as the py34 target. We have
> > also seen bug reports against some projects whose tests rely on stable
> > error messages from Python itself which isn't always the case across
> > version changes so these tests will need to be updated as well.
> > 
> > Note this change will not add python35 jobs for cases where projects
> > have special tox targets. This is restricted just to the default py35
> > unittesting.
> > 
> > As always let us know if you questions,
> > Clark
> 
> How soon can projects replace py34 with py35?
> 
> I tried py35 for neutron locally, and it ran without errors.
> 

I think we should be aggressive on python 3.5 vs. 3.4, since anywhere
that shipped 3.4 also shipped 2.7. Otherwise we end up wasting time on
whatever subtle differences there are.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] New Python35 Jobs coming

[Henry Gessau]

Clark Boylan  wrote:
> The infra team is working on taking advantage of the new Ubuntu Xenial
> release including running unittests on python35. The current plan is to
> get https://review.openstack.org/#/c/336272/ merged next Tuesday (July
> 5, 2016). This will add non voting python35 tests restricted to >=
> master/Newton on all projects that had python34 testing.
> 
> The expectation is that in many cases python35 tests will just work if
> python34 testing was also working. If this is the case for your project
> you can propose a change to openstack-infra/project-config to make these
> jobs voting against your project. You should only need to edit
> jenkins/jobs/projects.yaml and zuul/layout.yaml and remove the '-nv'
> portion of the python35 jobs to do this.
> 
> We do however expect that there will be a large group of failed tests
> too. If your project has a specific tox.ini py34 target to restrict
> python3 testing to a specific list of tests you will need to add a tox
> target for py35 that does the same thing as the py34 target. We have
> also seen bug reports against some projects whose tests rely on stable
> error messages from Python itself which isn't always the case across
> version changes so these tests will need to be updated as well.
> 
> Note this change will not add python35 jobs for cases where projects
> have special tox targets. This is restricted just to the default py35
> unittesting.
> 
> As always let us know if you questions,
> Clark

How soon can projects replace py34 with py35?

I tried py35 for neutron locally, and it ran without errors.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] New Python35 Jobs coming

[Doug Hellmann]

Excerpts from Clark Boylan's message of 2016-07-01 12:51:52 -0700:
> The infra team is working on taking advantage of the new Ubuntu Xenial
> release including running unittests on python35. The current plan is to
> get https://review.openstack.org/#/c/336272/ merged next Tuesday (July
> 5, 2016). This will add non voting python35 tests restricted to >=
> master/Newton on all projects that had python34 testing.
> 
> The expectation is that in many cases python35 tests will just work if
> python34 testing was also working. If this is the case for your project
> you can propose a change to openstack-infra/project-config to make these
> jobs voting against your project. You should only need to edit
> jenkins/jobs/projects.yaml and zuul/layout.yaml and remove the '-nv'
> portion of the python35 jobs to do this.
> 
> We do however expect that there will be a large group of failed tests
> too. If your project has a specific tox.ini py34 target to restrict
> python3 testing to a specific list of tests you will need to add a tox
> target for py35 that does the same thing as the py34 target. We have
> also seen bug reports against some projects whose tests rely on stable
> error messages from Python itself which isn't always the case across
> version changes so these tests will need to be updated as well.
> 
> Note this change will not add python35 jobs for cases where projects
> have special tox targets. This is restricted just to the default py35
> unittesting.
> 
> As always let us know if you questions,
> Clark
> 

This is good news. Python 3.4 is only supported for security updates at
this point [1], so we'll want to make it a priority to get 3.5 working
soon.

Doug

[1] https://mail.python.org/pipermail/python-announce-list/2016-June/011249.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] New Python35 Jobs coming

[Clark Boylan]

The infra team is working on taking advantage of the new Ubuntu Xenial
release including running unittests on python35. The current plan is to
get https://review.openstack.org/#/c/336272/ merged next Tuesday (July
5, 2016). This will add non voting python35 tests restricted to >=
master/Newton on all projects that had python34 testing.

The expectation is that in many cases python35 tests will just work if
python34 testing was also working. If this is the case for your project
you can propose a change to openstack-infra/project-config to make these
jobs voting against your project. You should only need to edit
jenkins/jobs/projects.yaml and zuul/layout.yaml and remove the '-nv'
portion of the python35 jobs to do this.

We do however expect that there will be a large group of failed tests
too. If your project has a specific tox.ini py34 target to restrict
python3 testing to a specific list of tests you will need to add a tox
target for py35 that does the same thing as the py34 target. We have
also seen bug reports against some projects whose tests rely on stable
error messages from Python itself which isn't always the case across
version changes so these tests will need to be updated as well.

Note this change will not add python35 jobs for cases where projects
have special tox targets. This is restricted just to the default py35
unittesting.

As always let us know if you questions,
Clark

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev