macOS releases do not use ccache and take 5.5 hours #4053

Activity

1. ryanaslett commented on Mar 27, 2025

   

   ryanaslett

   on Mar 27, 2025

   ContributorAuthor

   More actions

   We should be able to modify the release machines to symlink cc to ccache to cause the macos release builds to use ccache without modifying the makefile.
2. richardlau commented on Mar 27, 2025

   

   richardlau

   on Mar 27, 2025

   Member

   More actions

   FWIW we have some Ansible setup around ccache on macOS under the old, pre-ephemeral, setup:
   

   build/ansible/roles/baselayout/tasks/partials/ccache/macos.yml

   Lines 1 to 13 in a7a185f

   	- name: "ccache : check whether /etc/paths contains '/usr/local/opt/ccache/libexec' (macos)"
   	command: grep -Fxq "/usr/local/opt/ccache/libexec" /etc/paths
   	register: ccache_mac
   	check_mode: no
   	ignore_errors: yes
   	changed_when: no
   	- name: "ccache : add ccache to the path (macos)"
   	when: ccache_mac.rc == 1
   	lineinfile:
   	dest: "/etc/paths"
   	insertbefore: BOF
   	line: "/usr/local/opt/ccache/libexec"

   and explicitly adding to the PATH environment variable for the Jenkins agent:

   build/ansible/roles/jenkins-worker/templates/start.j2

   Line 11 in a7a185f

   export PATH="$(brew --prefix)/opt/ccache/libexec:$PATH"

   May be worth checking if symlinks for the compilers are automatically created in $(brew --prefix)/opt/ccache/libexec by the ccache install?

   👍React with 👍1Reacted by Ryan Aslett
3. ryanaslett commented on Mar 31, 2025

   

   ryanaslett

   on Mar 31, 2025

   ContributorAuthor

   More actions

   May be worth checking if symlinks for the compilers are automatically created in $(brew --prefix)/opt/ccache/libexec by the ccache install?

   Indeed they are.

   I have added $(brew --prefix)/opt/ccache/libexec to the path variables set in jenkins for the ephemeral instances (similar to the previous start.sh entrypoint), and now the release jobs use the ccache.

   Unfortunately, the release images were not configured to use the shared cache, and used the local cache and ran out of disk running the universal binary builds. (Example: https://ci-release.nodejs.org/job/iojs+release/10883/nodes=osx13-release-pkg/)

   I have reconfigured the release images, but am having difficulty saving the images due to some glitch in the orka cluster.

   I have an open support ticket with MacStadium to hopefully resolve the cluster issue so I can make the required config changes.

   Shout out/thanks to @iuuukhueeee for asking good questions to help get this fixed.

   ❤️React with ❤️1Reacted by Thien Nguyen
4. ryanaslett commented on Apr 1, 2025

   

   ryanaslett

   on Apr 1, 2025

   ContributorAuthor

   More actions

   Update: Have resolved the issues with the release images and they are now using the shared ccache.

   osx13-release-pkg build was down to 1 hour. Once all the versions have been rebuilt and re-fill the caches we should see releases back down to the "less than 1.5 hrs"

   🎉React with 🎉2Reacted by Richard Lau and Thien Nguyen
5. ryanaslett commented on Apr 2, 2025

   

   ryanaslett

   on Apr 2, 2025

   ContributorAuthor

   More actions

   The osx13-x64-release-tar took 26 minutes (was 2.25 -> 2.5 hrs before)
   https://ci-release.nodejs.org/job/iojs+release/nodes=osx13-x64-release-tar/10894/

   The osx13-arm64-release-tar took 5min 53 s (was ~50 min before: https://ci-release.nodejs.org/job/iojs+release/nodes=osx13-arm64-release-tar/10891/

   the osx13-release-pkg is coming in at 23 min (was ~ 5hrs and 5 min before: https://ci-release.nodejs.org/job/iojs+release/nodes=osx13-release-pkg/10891/)

   I think we can call this one done.

   🎉React with 🎉1Reacted by Thien Nguyen
6. ryanaslett

   closed this as completedon Apr 2, 2025