Mohammed Naser <mna...@vexxhost.com> writes: > On Wed, Nov 7, 2018 at 2:07 PM Dr. Jens Harbott (frickler) > <j.harb...@x-ion.de> wrote: >> >> 2018-11-07 12:47 GMT+00:00 Mohammed Naser <mna...@vexxhost.com>: >> > On Wed, Nov 7, 2018 at 1:37 PM Doug Hellmann <d...@doughellmann.com> wrote: >> >> >> >> Corey Bryant <corey.bry...@canonical.com> writes: >> >> >> >> > On Wed, Oct 10, 2018 at 8:45 AM Corey Bryant >> >> > <corey.bry...@canonical.com> >> >> > wrote: >> >> > >> >> > I'd like to start moving forward with enabling py37 unit tests for a >> >> > subset >> >> > of projects. Rather than putting too much load on infra by enabling 3 x >> >> > py3 >> >> > unit tests for every project, this would just focus on enablement of >> >> > py37 >> >> > unit tests for a subset of projects in the Stein cycle. And just to be >> >> > clear, I would not be disabling any unit tests (such as py35). I'd just >> >> > be >> >> > enabling py37 unit tests. >> >> > >> >> > As some background, this ML thread originally led to updating the >> >> > python3-first governance goal (https://review.openstack.org/#/c/610708/) >> >> > but has now led back to this ML thread for a +1 rather than updating the >> >> > governance goal. >> >> > >> >> > I'd like to get an official +1 here on the ML from parties such as the >> >> > TC >> >> > and infra in particular but anyone else's input would be welcomed too. >> >> > Obviously individual projects would have the right to reject proposed >> >> > changes that enable py37 unit tests. Hopefully they wouldn't, of course, >> >> > but they could individually vote that way. >> >> > >> >> > Thanks, >> >> > Corey >> >> >> >> This seems like a good way to start. It lets us make incremental >> >> progress while we take the time to think about the python version >> >> management question more broadly. We can come back to the other projects >> >> to add 3.7 jobs and remove 3.5 jobs when we have that plan worked out. >> > >> > What's the impact on the number of consumption in upstream CI node usage? >> >> I think the relevant metric here will be nodes_used * time_used. >> nodes_used will increase by one, time_used for usual unit test jobs >> seems to be < 10 minutes, so I'd think that the total increase in CI >> usage should be neglegible compared to full tempest or similar jobs >> that take 1-2 hours. > > Indeed it doesn't look too bad: > > http://zuul.openstack.org/builds?job_name=openstack-tox-py35 > > It'll be good to try and aim to transition as quickly as possible to > avoid extra 'wasted' resources in the infrastructure side
Right, I think we can live with it for a few weeks. -- Doug __________________________________________________________________________ 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