-
Notifications
You must be signed in to change notification settings - Fork 166
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
ansible: pin Python 3 to 3.10.8 #3062
Conversation
So far I've only run the updated playbook against these two machines. |
Fixed by passing Now the playbook breaks trying to download an icon:
|
Fixed that by pointing to the favicon from our Jenkins test CI instance instead of the mirrors.jenkins-ci.org URL. Also updated the agents to run on Temurin (Java) 17 (#3030). For now, updated playbook only applied to
I'll do the others tomorrow as there is the manual step to uninstall |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Download the Jenkins icon from our own CI server to avoid failure due to redirects.
Node.js 14 is incompatible with Python 3.11. Pin Python 3 to 3.10.8.
I've updated all of the Windows machines except for the arm64 machines. I was able to get a Node.js 14 build to pass: https://ci.nodejs.org/job/node-test-commit-windows-fanned/51761/ I've not been able to run this against the arm64 machines:
1: e.g.
Maybe this isn't required though for the arm64 machines as it doesn't look like https://ci.nodejs.org/job/windows-arm-simple/ can compile Node.js 14 anyway: https://ci.nodejs.org/job/windows-arm-simple/87/nodes=win10-vs2019-arm64/console |
Yes, I think we don't have to worry about Node.js 14 for Windows/Arm64. |
We are here to help if needed, and we actively monitor build and test of nodejs for main branch on our side through our nightly CI. It uses this script for build and test. |
Node.js 14 is incompatible with Python 3.11. Pin Python 3 to 3.10.8.
Run Jenkins agent on Java 17.
Updated Windows CI hosts:
Outdated
We're using chocolatey to manage Python on the Windows machines and https://ci.nodejs.org/job/windows-update-reboot/ has updated the Windows machines to Python 3.11.0. Unfortunately, this has broken Node.js 14 builds:
So far it looks like the Node.js 14 build is only broken on
even though other machines also appear to have been updated to Python 3.11.0. I think that is because those two machines were rebooted last week to try to solve disk space issues and the other machines will start to fail the next time they are rebooted.
In order to stop chocolatey updating Python 3 I've had to pin both
python
andpython3
packages (if I don'tcup -y all
still updates to Python 3.11.0). Unfortunately, to get the playbook to run the pinned task I had to uninstall Python 3.11.0 first:e.g.
However, although the updated playbook does install Python 3.10.8 and pins it (checked with
choco pin list
and verifiedcup -y all
doesn't update it) the playbook is now broken becausepy.exe
is missing:I think I'll need some help here.
cc @joaocgreis @nodejs/platform-windows