Re: [macports/macports-ports] Update pure and pure-docs to 0.66 (#350)

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [macports/macports-ports] Update pure and pure-docs to 0.66 (#350)

Aljaž Srebrnič-2
On 07 mar 2017, at 13:00, Albert Graef <[hidden email]> wrote:

There seems to be something going wrong with the buildbots. I'm getting a bunch of failures due to the build servers not being able to get the source tarballs from Bitbucket, even though they are all there and download all right for me. The errors look like this:

Error: Failed to fetch pure: Operation too slow. Less than 1024 bytes/sec transfered the last 60 seconds

@g5pw Do you have access to the build servers and see what's going on there?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

<script type="application/json" data-scope="inboxmarkup" class="">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/macports/macports-ports","title":"macports/macports-ports","subtitle":"GitHub repository","main_image_url":"<a href="https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png" class="">https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png</a>","avatar_image_url":"<a href="https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png" class="">https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png</a>","action":{"name":"Open in GitHub","url":"<a href="https://github.com/macports/macports-ports" class="">https://github.com/macports/macports-ports</a>"}},"updates":{"snippets":[{"icon":"PERSON","message":"@agraef in #350: There seems to be something going wrong with the buildbots. I'm getting a bunch of failures due to the build servers not being able to get the source tarballs from Bitbucket, even though they are all there and download all right for me. The errors look like this:\r\n\r\n~~~\r\nError: Failed to fetch pure: Operation too slow. Less than 1024 bytes/sec transfered the last 60 seconds\r\n~~~\r\n\r\n@g5pw Do you have access to the build servers and see what's going on there?"}],"action":{"name":"View Pull Request","url":"<a href="https://github.com/macports/macports-ports/pull/350#issuecomment-284702534" class="">https://github.com/macports/macports-ports/pull/350#issuecomment-284702534</a>"}}}</script>
Forwarding this to the -dev mailing list. It looks like the buildbots don’t have a reliable internet connection?


--
Aljaž Srebrnič a.k.a g5pw
My public key:  https://g5pw.me/key
Key fingerprint = 2109 8131 60CA 01AF 75EC  01BF E140 E1EE A54E E677

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [macports/macports-ports] Update pure and pure-docs to 0.66 (#350)

Ryan Schmidt-24

> On Mar 7, 2017, at 06:25, Aljaž Srebrnič <[hidden email]> wrote:
>
>> On 07 mar 2017, at 13:00, Albert Graef <[hidden email]> wrote:
>>
>> There seems to be something going wrong with the buildbots. I'm getting a bunch of failures due to the build servers not being able to get the source tarballs from Bitbucket, even though they are all there and download all right for me. The errors look like this:
>>
>> Error: Failed to fetch pure: Operation too slow. Less than 1024 bytes/sec transfered the last 60 seconds
>>
>> @g5pw Do you have access to the build servers and see what's going on there?
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub, or mute the thread.
>>
> Forwarding this to the -dev mailing list. It looks like the buildbots don’t have a reliable internet connection?

The buildbot's internet connection is reliable, but it is slow.

We don't mirror distfiles automatically right now. https://trac.macports.org/ticket/53347

This means each buildworker needs to download a copy of the source code from the original site, using up bandwidth. If the buildworkers are idle when a commit comes through, that means many buildworkers are trying to download the same file at the same time, which makes each download slower. In some cases, this could result in some of the downloads timing out. I have not seen this happen lately but I have seen it happen months ago when we first set the system up.

If you have a link to a buildbot log of this happening, I can take a look at it.

I can also mirror these distfiles manually.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [macports/macports-ports] Update pure and pure-docs to 0.66 (#350)

Albert Graef
On Tue, Mar 7, 2017 at 5:43 PM, Ryan Schmidt <[hidden email]> wrote:
If you have a link to a buildbot log of this happening, I can take a look at it.

I can also mirror these distfiles manually.


This then subsequently caused the pure-docs port to fail because pure was missing as a dependency: https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/26667

I think there were other instances of "Failed to fetch", but I don't remember them from the top of my head, I'd have to go digging in my mail box.

--
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email:  [hidden email]
WWW:    https://plus.google.com/+AlbertGraef
Loading...