On Monday, 26 March 2018 at 16:24:10 UTC, Atila Neves wrote:
> On Monday, 26 March 2018 at 15:34:12 UTC, Seb wrote:
>> On Monday, 26 March 2018 at 14:16:28 UTC, Atila Neves wrote:
>>> [...]
>>
>> Even with a recent DUB binary (e.g. 1.7.2 or 1.8.0)?
>> (=2.078.3 or 2.079.0)
>>
>> Anything that you are being able to reproduce with a "fake" always failing registry?
>>
>> In theory the recent DUB binaries comes with multiple backup mirrors and a more advanced retry logic.
>> We even have a few tests for this now, e.g.
>>
>> https://github.com/dlang/dub/blob/master/test/timeout.sh
>> https://github.com/dlang/dub/blob/master/test/fetchzip.sh
>
> Yes. Today it took too long to respond and my travis build failed because it was hung for >10min.
>
> Atila

Do you have a link by chance?

On Monday, 26 March 2018 at 18:28:09 UTC, Seb wrote:
> On Monday, 26 March 2018 at 16:24:10 UTC, Atila Neves wrote:
>> On Monday, 26 March 2018 at 15:34:12 UTC, Seb wrote:
>>> On Monday, 26 March 2018 at 14:16:28 UTC, Atila Neves wrote:
>>>> [...]
>>>
>>> Even with a recent DUB binary (e.g. 1.7.2 or 1.8.0)?
>>> (=2.078.3 or 2.079.0)
>>>
>>> Anything that you are being able to reproduce with a "fake" always failing registry?
>>>
>>> In theory the recent DUB binaries comes with multiple backup mirrors and a more advanced retry logic.
>>> We even have a few tests for this now, e.g.
>>>
>>> https://github.com/dlang/dub/blob/master/test/timeout.sh
>>> https://github.com/dlang/dub/blob/master/test/fetchzip.sh
>>
>> Yes. Today it took too long to respond and my travis build failed because it was hung for >10min.
>>
>> Atila
>
> Do you have a link by chance?

No, since I restarted the build as soon as I could reach code.dlang.org in the browser. I'm not sure how much information the link would be anyway. At the time the website was unresponsive instead of just not returning anything.

On Monday, 26 March 2018 at 15:34:12 UTC, Seb wrote:
> Even with a recent DUB binary (e.g. 1.7.2 or 1.8.0)?
> (=2.078.3 or 2.079.0)
>
> Anything that you are being able to reproduce with a "fake" always failing registry?
>
> In theory the recent DUB binaries comes with multiple backup mirrors and a more advanced retry logic.
> We even have a few tests for this now, e.g.
>
> https://github.com/dlang/dub/blob/master/test/timeout.sh
> https://github.com/dlang/dub/blob/master/test/fetchzip.sh

I experienced the same with dub 1.8.0. It never switched to one of the mirrors. Only `--registry=` option helped.

On Monday, 26 March 2018 at 18:28:09 UTC, Seb wrote:
> On Monday, 26 March 2018 at 16:24:10 UTC, Atila Neves wrote:
>> On Monday, 26 March 2018 at 15:34:12 UTC, Seb wrote:
>>> On Monday, 26 March 2018 at 14:16:28 UTC, Atila Neves wrote:
>>>> [...]
>>>
>>> Even with a recent DUB binary (e.g. 1.7.2 or 1.8.0)?
>>> (=2.078.3 or 2.079.0)
>>>
>>> Anything that you are being able to reproduce with a "fake" always failing registry?
>>>
>>> In theory the recent DUB binaries comes with multiple backup mirrors and a more advanced retry logic.
>>> We even have a few tests for this now, e.g.
>>>
>>> https://github.com/dlang/dub/blob/master/test/timeout.sh
>>> https://github.com/dlang/dub/blob/master/test/fetchzip.sh
>>
>> Yes. Today it took too long to respond and my travis build failed because it was hung for >10min.
>>
>> Atila
>
> Do you have a link by chance?

I was about to click on the rebuild button when I remembered you asked for this:

https://travis-ci.org/atilaneves/reggae/jobs/362076768

It's an effort for me to keep my OCD from wanting the build green. ;)

These kind of failures happen all the time.


Atila