We are seeing that macosx builds failing for 8u-cpu and 8u351 b03 builds.
On looking into the logs we could see that macosx release builds are failing on sign.sh file ,we have locally modified the file sign.sh to increase the timeout period from 60 to 600 post which the release builds have passed.

http://re-jdk8-jenkins-master.s1.javaplatfo1phx.oraclevcn.com:8080/job/8-2-build-macosx-x64/391/

5:27:36 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=32m; support was removed in 8.0
15:27:36 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=160m; support was removed in 8.0
15:28:37 [signing][Mon Jul 25 10:58:35 BST 2022] Warning: Timeout reached!
15:28:37 /System/Volumes/Data/jenkins/workspace/8-2-build-macosx-x64/jdk8u-cpu/2792/build/macosx-x64/sign.sh: line 150:


We have fixed locally for making our promotion builds to pass
bash-3.2$ diff -c sign.sh sign.sh_bkup
*** sign.sh Tue Jul 26 10:03:26 2022
--- sign.sh_bkup Tue Jul 26 10:01:57 2022
***************
*** 114,120 ****
      file_size_kb="$(du -k "$src" | cut -f1)"
      timeout="$(expr $file_size_kb / 200 || true)"
      if [ "$timeout" -lt "60" ]; then
! timeout="600"
      fi
      if [ "$client_command" = "mac_notarize" ]; then
          # Add a flat 10 minutes when notarizing
--- 114,120 ----
      file_size_kb="$(du -k "$src" | cut -f1)"
      timeout="$(expr $file_size_kb / 200 || true)"
      if [ "$timeout" -lt "60" ]; then
! timeout="60"
      fi
      if [ "$client_command" = "mac_notarize" ]; then
          # Add a flat 10 minutes when notarizing
bash-3.2$