[MacPorts] #62977: Build noarch ports on 11_arm64 builder

[MacPorts]

#62977: Build noarch ports on 11_arm64 builder
----------------------------+---------------------
  Reporter:  jmroot         |      Owner:  admin@…
      Type:  enhancement    |     Status:  closed
  Priority:  Normal         |  Milestone:
 Component:  buildbot/mpbb  |    Version:
Resolution:  fixed          |   Keywords:
      Port:                 |
----------------------------+---------------------

Comment (by jmroot):

 Replying to [comment:8 ryandesign]:
 > Right. But I think the worst that could happen is that one worker
 uploads its archive to master, which generates a signature for it and
 deploys both, and a short time later the second worker uploads its archive
 to master which generates a new signature and deploys both of those,
 wiping out the first one. That's probably fine.

 There are some comments in deploy_archives.sh that indicate that multiple
 build steps running on the buildmaster can run simultaneously, which is
 why a different upload directory name per worker is used. The worst that
 could happen is that worker 1 uploads an archive, the master signs it and
 starts deploying the two files, one of them is deployed, execution
 switches to worker 2's job which signs the archive and deploys both files,
 and then worker 1's job resumes and deploys its other file. There's then
 an archive from one worker and a signature from the other on the packages
 server. Unlikely perhaps, but I find that unlikely race conditions have a
 bad habit of happening in practice.

 There is some locking in deploy_archives.sh that is used in the case of a
 single shared upload directory. I think it would be safest to extend that
 to the multi-directory case as well.

-- 
Ticket URL: <https://trac.macports.org/ticket/62977#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS