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 google.com:80, which makes the test result
> > flaky.
> > 
> > Would you mind to consider setting up something locally (a small web
> > server) in testing environment to facilitate this test? If that's okay
> > I can help to cook a patch.
> 
> Yep, I was planning to run python simplehttpserver. If you are
> interested in preparing a patch you are more than welcome. :)

We now also have [1] the needs-internet restriction that you can use in
the mean time.

Paul

[1]
https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst



signature.asc
Description: OpenPGP digital signature


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 consider setting up something locally (a small web
> server) in testing environment to facilitate this test? If that's okay
> I can help to cook a patch.

Yep, I was planning to run python simplehttpserver. If you are
interested in preparing a patch you are more than welcome. :)


--abhijith



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 testing environment to facilitate this test? If that's okay
I can help to cook a patch.

Regards,
Aron