Opened 5 months ago

Closed 4 months ago

#29644 closed defect (duplicate)

Stem's integration test hangs

Reported by: teor Owned by: atagar
Priority: Medium Milestone:
Component: Core Tor/Stem Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Tor runs Stem's integration test as part of its CI.

It looks liken Stem or Tor hung on a controller test:

Starting /home/travis/build/torproject/tor/src/app/tor...
  Mar 04 02:35:25.793 [notice] Tor 0.4.0.2-alpha-dev (git-e5444ef2faba66ac) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1f, Zlib 1.2.8, Liblzma 5.1.0alpha, and Libzstd N/A.
  Mar 04 02:35:25.794 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
  Mar 04 02:35:25.794 [notice] This version is not a stable Tor release. Expect more bugs than usual.
  Mar 04 02:35:25.795 [notice] Read configuration file "/home/travis/build/torproject/tor/stem/test/data/torrc".
  Mar 04 02:35:25.801 [notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.
  Mar 04 02:35:25.801 [notice] Based on detected system memory, MaxMemInQueues is set to 5609 MB. You can override this by setting MaxMemInQueues by hand.
  Mar 04 02:35:25.801 [warn] ControlPort is open, but no authentication method has been configured.  This means that any program on your computer can reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.
  Mar 04 02:35:25.804 [notice] Opening Socks listener on 127.0.0.1:1112
  Mar 04 02:35:25.804 [notice] Opened Socks listener on 127.0.0.1:1112
  Mar 04 02:35:25.804 [notice] Opening Control listener on 127.0.0.1:1111
  Mar 04 02:35:25.804 [notice] Opened Control listener on 127.0.0.1:1111
  Mar 04 02:35:25.804 [notice] Opening OR listener on 0.0.0.0:1113
  Mar 04 02:35:25.804 [notice] Opened OR listener on 0.0.0.0:1113
  Mar 04 02:35:25.000 [notice] Configured to measure directory request statistics, but no GeoIP database found. Please specify a GeoIP database using the GeoIPFile option.
  Mar 04 02:35:26.000 [notice] Your Tor server's identity key fingerprint is 'Unnamed CAA75DC513889BD4B79AFC21428BAA59B2A466CB'
  Mar 04 02:35:26.000 [notice] Bootstrapped 0% (starting): Starting
  done (0 seconds)
Running tests...
  util.conf...                                         success (0.00s)
  util.connection...                                   success (0.00s)
  util.proc...                                         success (0.00s)
  util.system...                                       success (0.24s)
  interpreter...                                       success (6.21s)
  version...                                           success (0.76s)
  manual...                                            success (0.00s)
  directory.authority...                               success (0.00s)
  directory.fallback...                                success (0.00s)
  client.connection...                                 success (0.12s)
  response.protocolinfo...                             success (0.01s)
  socket.control_socket...                             success (0.02s)
  socket.control_message...                            success (0.06s)
  connection.authentication...                         success (0.01s)
  connection.connect...                                success (0.00s)
  control.base_controller...                           success (1.48s)
  control.controller...                               
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated

https://travis-ci.org/torproject/tor/jobs/501280583

Is this a Stem or a Tor issue?
What can we do to diagnose this issue?
How can we make Stem exit with failure, rather than hanging?
Do we need to collect and show debug logs in Tor's CI?
(We can't show the debug logs in CI unless Stem exits with a failure.)

Child Tickets

Change History (2)

comment:1 Changed 5 months ago by teor

I've only seen this issue once, so we might need to make changes to Stem, Tor, or CI, then wait for it to happen again.

comment:2 Changed 4 months ago by atagar

Resolution: duplicate
Status: newclosed

Hi teor, deduplicating this with #29437. Unfortunately the intermittent nature of this is gonna make it a real pita to troubleshoot. It would be helpful if we add '--log TRACE' to the test arguments so we have more information when this arises, but on the downside that will mean unpleasantly verbose output when troubleshooting other issues...

Note: See TracTickets for help on using tickets.