Update comments about python versions used in sanity checks

... to explain why we need these more clearly and precisely.

Change-Id: I9acffef0d85ccb0dfc2c5ebaba7f1c9c72c8435e
This commit is contained in:
Takashi Kajinami 2022-11-16 17:07:20 +09:00 committed by Sergii Golovatiuk
parent 6815b0fb1f
commit 1587c22d0a
1 changed files with 10 additions and 2 deletions

View File

@ -5,7 +5,11 @@
parent: tox
vars:
tox_envlist: sanity # dynamic tox env added by tox-ansible
# we want to run sanity only on py3.10 instead of implicit 2.6-3.9 range
# We need to use the proper python version depends on the Ansible
# version (For example python 3.10 requires Ansible >=2.13). As we pin
# Ansible version for sanity environemnt in tox.ini, we pin python
# version here. Python 3.10 is now the default Python version in Jammy
# and we need to revisit this when we migrate this job to a new version.
tox_extra_args: -- --python 3.10
- job:
@ -14,7 +18,11 @@
parent: tox
vars:
tox_envlist: units # dynamic tox env added by tox-ansible
# we want to run sanity only on py3.10 instead of implicit 2.6-3.9 range
# We need to use the proper python version depends on the Ansible
# version (For example python 3.10 requires Ansible >=2.13). As we pin
# Ansible version for sanity environemnt in tox.ini, we pin python
# version here. Python 3.10 is now the default Python version in Jammy
# and we need to revisit this when we migrate this job to a new version.
tox_extra_args: -- --python 3.10
- job: