canonical-ci-engineering team mailing list archive
-
canonical-ci-engineering team
-
Mailing list archive
-
Message #01171
squid.internal proxy for udtc-trusty-tests
Didier,
I checked the operation of the squid proxy manually from the udtc test VMs
and all looks well right now:
ubuntu@ps-trusty-desktop-amd64-1:/tmp$ https_proxy="
https://squid.internal:3128/
" wget https://developer.android.com/sdk/index.html
--2015-09-24 13:56:15-- https://developer.android.com/sdk/index.html
Resolving squid.internal (squid.internal)... 91.189.89.33
Connecting to squid.internal (squid.internal)|91.189.89.33|:3128...
connected.
Proxy request sent, awaiting response... 200 OK
Length: 72747 (71K) [text/html]
Saving to: ‘index.html’
100%[======================================>] 72,747 163KB/s in
0.4s
2015-09-24 13:56:16 (163 KB/s) - ‘index.html’ saved [72747/72747]
I also checked with IS and they reported no recent issues with
squid.internal or the firewall route between it and the ci network.
If this continues to be a problem, can we add a check to udtc-trusty-tests
to verify the proxy is operational?
Thanks,
Francis
--
Francis Ginther
Canonical - Ubuntu Engineering - Continuous Integration Team
Follow ups