On Wednesday, March 22, 2017 9:53:26 AM CET Tim Ruehsen wrote: > On Wednesday, March 22, 2017 2:02:30 PM CET Avinash Sonawane wrote: > > On Wed, Mar 22, 2017 at 1:49 PM, Tim Ruehsen <[email protected]> wrote: > > >> Also I see many "Failed to resolve 'http:80 (Name or service not > > >> known)" in tests/test-suite.log > > > > > > Should be http://localhost:80 ... > > > > As I don't have earlier test-suite.log which contained the log for all > > 31 tests. And also since I hadn't installed autogen earlier I'm > > installing all the dependencies and wget2 from scratch. I'll then run > > the tests again and will get back to you. > > > > > what does this output: > > > $ set|grep -i prox > > > > It shows all my environment variables with proxy set to them. > > Here's complete output http://pastebin.com/UNPcgRHC > > Quite interesting. I'll set up a similar environment and give it a try. > I am sure, we don't parse 'no_proxy'. So maybe your proxy settings have a > wrong impact on the tests. We should call 'wget2' in the test suite with > --no- proxy and/or respect the no_proxy environment variable.
Yup, that's it. $ cd tests $ http_proxy='http://192.168.8.253:3128/' ./test-i-http And it hangs... I'll create one or two issues... if you like to, work on these. They are blockers for you, you have the best test environment. And they are easy to fix. Regards, Tim
signature.asc
Description: This is a digitally signed message part.
