build.macports.org failures

Ryan Schmidt ryandesign at macports.org
Thu Dec 12 12:20:41 PST 2013


On Dec 12, 2013, at 00:28, Joshua Root <jmr at macports.org> wrote:

> On 2013-12-11 16:47 , Joshua Root wrote:
>> On 2013-12-11 14:29 , Clemens Lang wrote:
>>> I've been monitoring the current attempt at building the remaining ports
>>> and it seems the buildbot is currently hanging at the valgrind-devel
>>> port. It *should* be running a post-fetch phase from the Portfile that
>>> uses the svn protocol to check out some sources, but I don't see any
>>> progress in the log anymore[1].
>>> 
>>> Could you maybe just kill the port process (or the svn process, if
>>> that's still running) on the Mavericks slave? It doesn't matter if the
>>> valgrind-devel build fails in this case, because valgrind-devel will not
>>> build on Mavericks anyway.
>>> 
>>> [1] The log is currently at about 2.1 GiB. Seems unlikely it would start
>>>    to cause problems at this size.
>> 
>> It didn't bring down the system, just made the build step fail due to
>> timeout as expected. That isn't great of course, and valgrind-devel
>> should be fixed to not hang, but gathering archives is currently
>> underway despite the failure, as designed.
>> 
>> I'll do a build with the last few hundred ports once it finishes up.
> 
> It seems textmate2 and yap-devel also hung. Both of these fetch with git.

textmate2 is unusual. In addition to fetching git submodules in a post-fetch block, the build system also fetches additional software during the build phase.



More information about the macports-dev mailing list