-
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
issues with node-test-commit-osx #3116
Comments
cc @nodejs/build |
that's because all |
Welp macstadium have decided to update the cluster this week instead of january when I booked the timeslot in for. |
I actually got a green one but the results weren't communicated back to the parent job, so it gets stuck there: https://ci.nodejs.org/job/node-test-commit-osx/49256/ |
I will try to re-deploy the testing VMs |
Current situation:
|
The test-orka-macos10.14-x64-1 agent in Jenkins is on a macOS 10.14 host: |
At this point all the Orka machines are up and running. We keep working on Orka in a separate discussion #3112 |
Big thank you to everyone involved! |
It seems that all macs are now back on Java 8. How is that? |
Confirmed @targos, We have Java 8 in all the Orka machines (10.x and 11):
The current vms are restored from an old backup available in Orka and I had some issues running ansibe (#3119). Yesterday I run Ansible successfully against the macos11 vms. I just realized that I run an old version of the playbook that didn't include your changes in #3085. So, I will pull the last changes in |
Thanks for you support @targos! 🙌 I managed to upgrade to Java 11 in macos11 machines. For 10.x I need to to finish a little patch before moving to Java 11 |
Confirmed. After manual patching, all the Orka machines (10.14, 10.15 and 11) are in the correct Java versions 🥳 |
We're not getting any successful buils through on node-test-commit-osx since at least 2 days ago.
The text was updated successfully, but these errors were encountered: