Public bug reported: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/t/thin/20210701_004508_69a07@/log.gz
Five test cases fail on armhf for thin/1.8.0-1 (thin/1.7.2-1build1 is fine): 1) Thin::Server on TCP socket should POST from Net::HTTP Failure/Error: expect(post('/', :arg => 'pirate')).to include('arg=pirate') expected "<!DOCTYPE html PUBLIC \"-//W3C//DTD HTML 4.01//EN\" \"http://www.w3.org/TR/html4/strict.dtd\">\n<htm...021 00:44:47 GMT by cremona (squid/3.5.27)</p>\n<!-- ERR_CONNECT_FAIL -->\n</div>\n</body></html>\n" to include "arg=pirate" ... +<h2>The requested URL could not be retrieved</h2> +<p>The following error was encountered while trying to retrieve the URL: <a href="http://0.0.0.0:3333/">http://0.0.0.0:3333/</a></p> +<p><b>Connection to 0.0.0.0 failed.</b></p> +<p id="sysmsg">The system returned: <i>(111) Connection refused</i></p> 2) Thin::Server on TCP socket should handle big POST Failure/Error: expect(post('/', :big => big)).to include(big) expected "<!DOCTYPE html PUBLIC \"-//W3C//DTD HTML 4.01//EN\" \"http://www.w3.org/TR/html4/strict.dtd\">\n<htm...021 00:44:47 GMT by cremona (squid/3.5.27)</p>\n<!-- ERR_CONNECT_FAIL -->\n</div>\n</body></html>\n" to include "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" ... +<h2>The requested URL could not be retrieved</h2> +<p>The following error was encountered while trying to retrieve the URL: <a href="http://0.0.0.0:3333/">http://0.0.0.0:3333/</a></p> +<p><b>Connection to 0.0.0.0 failed.</b></p> +<p id="sysmsg">The system returned: <i>(111) Connection refused</i></p> 3) Thin::Server on TCP socket should retreive remote address Failure/Error: expect(get('/')).to include('"REMOTE_ADDR"=>"127.0.0.1"') expected "<!DOCTYPE html PUBLIC \"-//W3C//DTD HTML 4.01//EN\" \"http://www.w3.org/TR/html4/strict.dtd\">\n<htm...021 00:44:47 GMT by cremona (squid/3.5.27)</p>\n<!-- ERR_CONNECT_FAIL -->\n</div>\n</body></html>\n" to include "\"REMOTE_ADDR\" => \"127.0.0.1\"" ... +<h2>The requested URL could not be retrieved</h2> +<p>The following error was encountered while trying to retrieve the URL: <a href="http://0.0.0.0:3333/">http://0.0.0.0:3333/</a></p> +<p><b>Connection to 0.0.0.0 failed.</b></p> +<p id="sysmsg">The system returned: <i>(111) Connection refused</i></p> 4) Thin::Server with threads should process request Failure/Error: raise "Reactor still running, wtf?" if EventMachine.reactor_running? RuntimeError: Reactor still running, wtf? # ./spec/spec_helper.rb:209:in `stop_server' # ./spec/server/threaded_spec.rb:25:in `block (2 levels) in <top (required)>' 5) Thin::Server with threads should process requests when blocked Failure/Error: expect(@requests).to eq(1) expected: 1 got: 0 (compared using ==) # ./spec/server/threaded_spec.rb:20:in `block (2 levels) in <top (required)>' Debian does not appear to be seeing these failures on armhf: https://buildd.debian.org/status/fetch.php?pkg=thin&arch=armhf&ver=1.8.0-1&stamp=1611145895&raw=0 The first recorded autopkgtest for 1.8.0-1 was April 2021, soon after impish opened. The "ERR_CONNECT_FAIL" in the first three cases show Squid is hitting a Connection refused on armhf for some reason. I don't know if failures #4 and #5 are related but probably not a bad guess to assume they are. Perhaps setting up a squid proxy environment would allow reproduction? https://wiki.ubuntu.com/ProposedMigration#I.27m_seeing_a_squid_proxy.3F__My_tests_behave_differently_there.21 ** Affects: thin (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939086 Title: autopkgtest failures due to squid "(111) Connection refused" on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thin/+bug/1939086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs