[MacPorts] #44939: Buildots failed to build PyPy for SnowLeopard, Lion and MountainLion because of a strict timeout

[MacPorts]

#44939: Buildots failed to build PyPy for SnowLeopard, Lion and MountainLion
because of a strict timeout
----------------------------+--------------------------------
  Reporter:  macosx12345@…  |      Owner:  macports-tickets@…
      Type:  defect         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.3.1
Resolution:                 |   Keywords:
      Port:  pypy           |
----------------------------+--------------------------------

Comment (by ryandesign@…):

 As I understand it, our 4 buildslaves are virtual machines running on a
 single physical Mac. And when a revision is committed, a build is kicked
 off on all buildslaves simultaneously, so they're all competing for the
 same physical resources. I'm not sure if the pypy build uses multiple
 processor cores, but if it does, only ¼ of them would actually be
 available when the 4 buildslaves are going at it at the same time.

 I forced a build of pypy on the Mountain Lion buildslave only, and it
 succeeded after 2 hours 45 minutes. Same on the Snow Leopard buildslave.
 These binary packages are now available. I've tried the same on the Lion
 buildslave twice now, and it failed both times after over 2 hours. It
 could be that the older version of clang on the Lion server takes longer
 to compile, pushing this particular object over the 20-minute limit we've
 set.

 It does seem pretty egregious that any build system would work for over 20
 minutes without any output at all. Are the developers of pypy aware they
 are doing this?

 We could increase this timeout on the buildbot, but what value should we
 set it to?

-- 
Ticket URL: <https://trac.macports.org/ticket/44939#comment:2>
MacPorts <http://www.macports.org/>
Ports system for OS X