Public bug reported:

Currently we run cloud-init's unit tests twice in Travis:

* once on Python 3.6 with the latest versions of our dependencies from PyPI, and
* once on Python 3.5 with the versions of our dependencies that are in xenial 
(but installed from PyPI, rather than apt)

We currently know that cloud-init is run on 3.7 and 3.8, because eoan
and focal use those versions respectively.

We should expand our matrix of testing to cover all currently-supported
Python versions, 3.4+.

** Affects: cloud-init
     Importance: Medium
         Status: Triaged


** Tags: bitesize

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1874866

Title:
  Add more Python versions to cloud-init's Travis CI

Status in cloud-init:
  Triaged

Bug description:
  Currently we run cloud-init's unit tests twice in Travis:

  * once on Python 3.6 with the latest versions of our dependencies from PyPI, 
and
  * once on Python 3.5 with the versions of our dependencies that are in xenial 
(but installed from PyPI, rather than apt)

  We currently know that cloud-init is run on 3.7 and 3.8, because eoan
  and focal use those versions respectively.

  We should expand our matrix of testing to cover all currently-
  supported Python versions, 3.4+.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1874866/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to