-
Couldn't load subscription status.
- Fork 330
Changes in github workflow #363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
RHEL-8 system python is 3.6... I don't think we can drop support for it...
and python 2.6 failures are weird... that stuff should be running on centos 6, ubuntu shouldn't enter the picture...
It worked with 2.6 so it should continue to work, if anything, it's the CI environment that is broken, not the code
Okay, thank you, I will investigate Python 2.6 further.
About Python 3.6, the Ubuntu 22 image in GitHub does not support it (and is not planning to, according to this discussion).
Should it then be installed manually (adjust ci.yml to download and install it)?
I think we can use a RHEL image for it, just as we do for 2.6?
ad607fc to
ec44ed5
Compare
-ensure working pip on python2.7 -adjust python 3.6 to run on centos:8, since ubuntu22 image does not support python3.6 -git version on centos:6 was too old and was not working properly, changing it to manually download and build newer git version
ec44ed5 to
c4f0df1
Compare
Uh oh!
There was an error while loading. Please reload this page.
Summary:
There are several changes in ci.yml to ensure proper functioning.
Reasoning:
The Ubuntu 20.04 Actions runner image is now deprecated in github, so those were changed to the Ubuntu 22.04 image. The merge request as well has changes to ensure working pip on Python 2.7.
Having Python 3.6 in CentOS:8 container:
Python 3.6 is not supported on Ubuntu 22 or newer runners. The change adjusts the tests to be run with Python 3.6 in the CentOS:8 container.
Downloading and building git in centOS:6:
Unit tests failed to run due to the error messages, including ImportError and TypeError. Those can be found in action run .
The problem occurred due to an old version of git provided in CentOS 6. To solve the problem, the changes provide the installation of a newer git version.