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 failed log > |autopkgtest [17:03:58]: test command3: httping -F -c 4 http://google.com > |autopkgtest [17:03:58]: test command3: [----------------------- > |PING google.com:80 (/): > |connect time out > | > |connect time out > | > |connect time out > | > |connect time out > | > |--- http://google.com/ ping statistics --- > |4 connects, 0 ok, 100.00% failed, time 124118ms > |autopkgtest [17:06:02]: test command3: -----------------------] > |autopkgtest [17:06:02]: test command3: - - - - - - - - - - results - - - - > - - - - - - > |command3 FAIL non-zero exit status 127 > |autopkgtest [17:06:02]: @@@@@@@@@@@@@@@@@@@@ summary > |command1 PASS > |command2 PASS > |command3 FAIL non-zero exit status 127 > > it seems to have failed because the test is not allowed to connect to > the internet (or google itself). > Could it be verified what the test policy is in regard to network access > and then > - run the test again once CI enabled network access on all nodes > - removed that test from CI.
httping -F -c 4 http://google.com was kind of off hand smoke test. It was working in amd64 ci and I didn't bothered to look in to other archs. I will try to run some simple http server locally and ping to that. --abhijith
