Le 28/09/2015 23:18, Francis Ginther a écrit : > 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 >
Thanks Francis to look into this! Interesting, I wonder if there is anything in the datacenter which changes (as you can see, the latest release was working perfectly well: https://jenkins.qa.ubuntu.com/job/udtc-trusty-tests/1929 /label=ps-trusty-desktop-amd64-1,type=large/ (15.09.2~trusty1) and then it started to fail with exactly the same package version: https://jenkins.qa.ubuntu.com/job/udtc-trusty-tests/1959/label=ps-trusty-desktop-amd64-1,type=large/. Look at ubuntu-make release version, it's the same, so not a recent change here. Is there anything that changed into our datacenter internal squid? It can also be a package in trusty (I have the list of installed package) as we didn't see that issue and a new error popup on launchpad as you listed. I guess the next step for me would be to use a ssh access to the machine, do you mind guiding me in getting a ssh access to the machine so that I can inspect them directly? Cheers, Didier -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
