[Bug 1939086] Re: autopkgtest failures due to squid "(111) Connection refused" on armhf

2021-10-04 Thread Launchpad Bug Tracker
This bug was fixed in the package thin - 1.8.0-1ubuntu1

---
thin (1.8.0-1ubuntu1) impish; urgency=medium

  * Fix autopkgtest failure on armhf (LP: #1939086).
- d/ruby-tests.rake: Unset http_proxy env variable.
- d/p/increase-wait-time-for-server-stop.patch: Increase timeout
  when waiting for server to stop.

 -- Sergio Durigan Junior   Tue, 31 Aug
2021 15:40:13 -0400

** Changed in: thin (Ubuntu)
   Status: New => Fix Released

-- 
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

[Bug 1939086] Re: autopkgtest failures due to squid "(111) Connection refused" on armhf

2021-08-31 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/thin/+git/thin/+merge/407931

-- 
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

[Bug 1939086] Re: autopkgtest failures due to squid "(111) Connection refused" on armhf

2021-08-31 Thread Sergio Durigan Junior
I spent some time investigating this bug, and my conclusion is that the
problem lies elsewhere (i.e., it's not related to http_proxy being set).

In a nutshell, what I found is that the delay used in the "stop_server"
procedure is too low for armhf machines.  Here's the code in question:

200   def stop_server
201 @server.stop!
202 @thread.kill
203 
204 100.times do
205   break unless EM.reactor_running?
206   sleep 0.01
207 end
208 
209 raise "Reactor still running, wtf?" if EventMachine.reactor_running?
210   end

As can be seen, there's a 1 second delay to let the server actually
stop.  This seems to be enough in all architectures but armhf.

I don't know why the same problem doesn't manifest on Debian.  Maybe
because they have bare metal armhf servers, whereas we use lxd instances
inside arm64 machines?

Anyway, I was able to verify that if we extend this delay to, say, 10
seconds, the tests pass on armhf.  I also think that's something OK to
do, especially because the loop is actively checking if the server has
stopped and will break the loop if that's the case.

I'll put an MP up soon.

-- 
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

[Bug 1939086] Re: autopkgtest failures due to squid "(111) Connection refused" on armhf

2021-08-27 Thread Steve Langasek
I believe the problem here is that ruby honors http_proxy, but does not
honor no_proxy; so because we're in an environment requiring a proxy,
requests that are supposed to go to localhost are sent to the squid
proxy instead.

What I'm not clear on is why this works on runners *except* for armhf,
since all of these runners set http_proxy.

Unfortunately, gem2deb-test-runner does not have support for overriding
the environment the way that pkg-perl-autopkgtest does (via
debian/tests/pkg-perl/smoke-env).

Someone who knows ruby could modify the tests to unset http_proxy from
the environment, which ought to address the problem.

-- 
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

[Bug 1939086] Re: autopkgtest failures due to squid "(111) Connection refused" on armhf

2021-08-18 Thread Simon Chopin
For reference, the Debian autopkgtest run (successful) can be found here
: https://ci.debian.net/packages/t/thin/testing/armhf/

-- 
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