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
add win/arm64 factory classes and build worker #288
Conversation
master/custom/builders.py
Outdated
|
||
# Windows/arm64 | ||
("ARM64 Windows", "linaro-win-arm64", WindowsARM64Build, STABLE), | ||
("ARM64 Windows Non-Debug", "linaro-win-arm64", WindowsARM64ReleaseBuild, STABLE), |
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.
Please start with UNSTABLE. I prefer to wait until it is reliable before marking them as STABLE.
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.
Sure. I've added a new patch to mark the workers as UNSTABLE
Merged. The config will be deployed in the next cron task (in 1h? I'm not sure). |
Thanks, Victor! |
ARM64 Windows 3.x first green build: https://buildbot.python.org/all/#/builders/729/builds/2 ARM64 Windows Non-Debug 3.x orange build (success, test_asyncio random failure, it's a known issue): https://buildbot.python.org/all/#/builders/730/builds/3 |
win/arm64 buildbot worker has been up for nearly 10 days now. Except for the known intermittent issue for test_asyncio rest looks fine to me. @vstinner Is it a good time to mark the buildbot worker as stable? |
@pablogsal is the Python 3.10 and 3.11 release manager. I prefer to delegate the decision to him :-) |
I am fine marking it as stable, can you open a PR for it? |
The change adds factory classes for windows/arm64 platforms and adds build worker
linaro-win-arm64