On 14/07/2014 7:08 PM, [email protected] wrote:
> Am 14.07.2014 04:54, schrieb Ryan Kelly:
>> You could try editing the Makefile to pass the --timeout option directly
>> to pip. Where we currently have:
>>
>> INSTALL = $(ENV)/bin/pip install
>>
>> Add an argument to it like so:
>>
>> INSTALL = $(ENV)/bin/pip install --timeout=60
>>
>> Pip also appears to have a --proxy option which may be useful for you,
>> try adding it in the Makefile like:
>>
>> INSTALL = $(ENV)/bin/pip install --proxy="user:[email protected]:port"
>>
> Thank You for the reply.
>
> No, this helped not - nothing changed. When I added the environment
> variable PIP_DEFAULT_TIMEOUT of 60 seconds the timeout changed from 15
> seconds to about 20 seconds. So it's obvious that the timeout parameter
> to pip has it's effect, but there must be another timeout of 20 seconds
> (from which component?) that overrules the 60 seconds of pip.
>
> The proxy server is successfully used, I see that in the logilfe.
>
> Which component could overrule the 60 second timeout of pip with these
> 20 seconds?
I can't think of anything off the top of my head. Please attach the
full output from the `make build` command and I'll dig through to see
what I can find.
Cheers,
Ryan
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
