Bug#955535: Bug #955535: httping: flaky autopkgtest: PING google.com:80

2020-04-23 Thread Paul Gevers
Hi Abhijith, On Fri, 10 Apr 2020 19:19:20 +0530 Abhijith PA wrote: > On 03/04/20 7:24 am, Aron Xu wrote: > > Hi, > > > > The two different results are caused by different CI workers - some of > > our workers at ci.d.n does not have reliable network to public > > services, in this case to

Bug#955535: Bug #955535: httping: flaky autopkgtest: PING google.com:80

2020-04-10 Thread Abhijith PA
Hi Aron On 03/04/20 7:24 am, Aron Xu wrote: > Hi, > > The two different results are caused by different CI workers - some of > our workers at ci.d.n does not have reliable network to public > services, in this case to google.com:80, which makes the test result > flaky. > > Would you mind to

Bug#955535: httping: flaky autopkgtest: PING google.com:80

2020-04-10 Thread Abhijith PA
Thanks for reporting. On 02/04/20 12:26 pm, Sebastian Andrzej Siewior wrote: > Source: httping > Version: 2.5-5 > Severity: serious > Tags: sid bullseye > User: debian...@lists.debian.org > Usertags: flaky > > The test for httping passed on amd64[0] and failed on arm64[1]. Looking > at the

Bug#955535: Bug #955535: httping: flaky autopkgtest: PING google.com:80

2020-04-02 Thread Aron Xu
Hi, The two different results are caused by different CI workers - some of our workers at ci.d.n does not have reliable network to public services, in this case to google.com:80, which makes the test result flaky. Would you mind to consider setting up something locally (a small web server) in

Bug#955535: httping: flaky autopkgtest: PING google.com:80

2020-04-02 Thread Sebastian Andrzej Siewior
Source: httping Version: 2.5-5 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: flaky The test for httping passed on amd64[0] and failed on arm64[1]. Looking at the failed log |autopkgtest [17:03:58]: test command3: httping -F -c 4 http://google.com |autopkgtest