canonical-ci-engineering team mailing list archive

[Francis Ginther <francis.ginther@xxxxxxxxxxxxx>]

Didier,

The debug code shows that the proxy is accessible before and after running
the actual udtc tests [2]. The debug code shows that one of the URLs
accessed by the test is accessible with wget (and downloads a file as
'proxy-test.html'). While looking for some other possibilities, I found a
public bug report [3] which matches the error being seen on the s-jenkins
tests. I'm guessing this new bug report has the same root cause as the test
failures, but on different networks.

[2] -
http://s-jenkins.ubuntu-ci:8080/job/udtc-trusty-tests/1957/label=ps-trusty-desktop-amd64-1,type=large/console
[3] -
https://bugs.launchpad.net/ubuntu/+source/ubuntu-developer-tools-center/+bug/1499890

Francis

On Mon, Sep 28, 2015 at 11:19 AM, Francis Ginther <
francis.ginther@xxxxxxxxxxxxx> wrote:

> Didier,
>
> I've added some debug code to test the proxy connection before and after
> running the udtc tests [1]. The test is a simple one to make sure that
> https://developer.android.com/sdk/index.html is accessible. It is not
> when the proxy is not used.
>
> So far the proxy is working prior to running the tests.
>
> [1] - http://s-jenkins.ubuntu-ci:8080/job/udtc-trusty-tests/
>
> Francis
>
> On Mon, Sep 28, 2015 at 2:03 AM, Didier Roche <didier.roche@xxxxxxxxxxxxx>
> wrote:
>
>> Le 25/09/2015 08:44, Didier Roche a écrit :
>> > Le 24/09/2015 17:06, Francis Ginther a écrit :
>> >> 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?
>> >>
>> > Hey Francis,
>> >
>> > I still have the problem, look at the latest udtc-trusty-tests jobs. the
>> > http proxy configuration is still there and didn't change.
>> >
>> > Feel free to modify this job to get any debug info you can fetch, I
>> > can't use it until this is fixed (the small/medium tests are of little
>> > use alone) :)
>> > Thanks!
>> > Didier
>>
>>
>> Did you get any chance to look at that on Friday? The jobs are now
>> always failing (can be something in the config/machine that changed), do
>> you have time for us to look at that together today?
>> Cheers,
>> Didier
>>
>
>
>
> --
> Francis Ginther
> Canonical - Ubuntu Engineering - Continuous Integration Team
>



-- 
Francis Ginther
Canonical - Ubuntu Engineering - Continuous Integration Team