On 10/10/2018 15.42, Corey Bryant wrote:
On Wed, Oct 10, 2018 at 9:26 AM Andreas Jaeger <a...@suse.com
<mailto:a...@suse.com>> wrote:
On 10/10/2018 14.45, Corey Bryant wrote:
> [...]
> == Enabling py37 unit tests ==
>
> Ubuntu Bionic (18.04 LTS) has the 3.7.0 interpreter and I have
reviews
> up to define the py37 zuul job and templates here:
> https://review.openstack.org/#/c/609066
>
> I'd like to start submitting reviews to projects to enable
> openstack-python37-jobs (or variant) for projects that already have
> openstack-python36-jobs in their .zuul.yaml, zuul.yaml,
> .zuul.d/project.yaml.
We have projects testing python 3.5 and 3.6 already. Adding 3.7 to
it is
a lot of wasted VMs. Can we limit testing and not test all three,
please?
Well, I wouldn't call any of them wasted if they're testing against a
supported Python version.
What I mean is that we run too into a situation where we have a large
backlog of CI jobs since we have to many changes and jobs in flight.
So, I'm asking whether there is a good way to not duplicating all jobs
to run on all three interpreters. Do we really need testing of all three
versions? Or is testing with a subset a manageable risk?
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
