<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">I finally created a workaround [1] that lets the build bot know the build is not stuck and after several hours the builds now terminate [2]! However, I still don’t see the newly built binaries appear in <a href="http://packages.macports.org/ompl/" class="">http://packages.macports.org/ompl/</a>. Is this just a matter of mirrors having to catch up?<div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Mark<br class=""><br class="">[1] <a href="https://github.com/macports/macports-ports/commit/f110e5ed3d7ad46f47ad64042f150bcfc07f8c17" class="">https://github.com/macports/macports-ports/commit/f110e5ed3d7ad46f47ad64042f150bcfc07f8c17</a></div><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">[2] <a href="https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/21544" class="">https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/21544</a></div><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Mar 4, 2017, at 2:52 PM, Mojca Miklavec <<a href="mailto:mojca@macports.org" class="">mojca@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 4 March 2017 at 20:20, Mojca Miklavec wrote:<br class=""><blockquote type="cite" class="">On 4 March 2017 at 20:12, Mark Moll wrote:<br class=""><blockquote type="cite" class="">Hi,<br class=""><br class="">For one of the packages I maintain, ompl, there are no recent binary packages, despite the port being redistributable. I suspect it’s due to a build time-out. The Python binding generation for the C++ library can take an hour or two during which very little output is generated. Is it possible to force an increase in build time for a particular build?<br class=""></blockquote><br class="">Let's wait for a quiet moment at buildbots, rerun a build of that port<br class="">and see what happens.<br class=""></blockquote><br class=""><a href="https://build.macports.org/builders/ports-10.12_x86_64-watcher/builds/4029" class="">https://build.macports.org/builders/ports-10.12_x86_64-watcher/builds/4029</a><br class="">https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/22307<br class=""><br class="">Mojca<br class=""><br class=""></div></div></blockquote></div><br class=""></div></div></body></html>