-
Notifications
You must be signed in to change notification settings - Fork 167
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
macOS release jobs cannot start #4012
Comments
CC @ryanaslett FYI This would block the (delayed from last week) Node.js 20.18.3 proposal (cc @marco-ippolito ). |
I had modified the test jenkins cloud settings so that it could only provision 3 of the 4 vm's for each architecture in order to ensure that release always had capacity to provision a new instance. In doing so, jenkins stranded an instance, so even though the test jenkins was only aware of 3 instances, orka had 4 provisioned, thus there was no capacity for release. I remedied this yesterday, and all the builds have caught back up. |
Thanks! |
We still having some issues https://ci-release.nodejs.org/job/iojs+release/10793/ on for the job |
Jenkins was still having counting issues with how many nodes it thought it had vs how many it actually was allowed to manage, as such, the test instance had all of the x86 resources when the release was happening. Can we coordinate when the release does go out so that Im aware/available? I'm not seeing these github pings in a timely fashion, and I would like to be on hand to ensure it goes smoothly. |
I'd reschedule the v20.x release for monday |
v20.18.3 release went smoothly today. I'll try to release v22.14.0 tomorrow, hoping for the best |
Example: https://ci-release.nodejs.org/job/iojs+release/nodes=osx13-release-pkg/
The text was updated successfully, but these errors were encountered: