Opened 5 weeks ago

Last modified 15 hours ago

#29437 needs_information defect

test-stem times out intermittently

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


  control.base_controller...                           success (1.23s)
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:
The build has been terminated

Child Tickets

Change History (8)

comment:1 Changed 5 weeks ago by atagar

Hi rl1987. I've seen that from time to time too but haven't dug in since it's pretty infrequent. Lack of a consistent repro is going to make this a bit troublesome to solve.

First step if someone would care to dig in is to run our tests with '--verbose --log TRACE' until we get a hang and attach the output for the controller tests.

comment:2 Changed 5 weeks ago by atagar

Status: newneeds_information

comment:3 Changed 13 days ago by atagar

Component: Core Tor/TorCore Tor/Stem

comment:4 Changed 13 days ago by atagar

Another report of this: #29644

comment:5 Changed 11 days ago by teor

How verbose are the logs?

Our CI has a 10,000 line log limit, and we're already around 5,000.

Normally, we would send the logs to a file, then tail them on error. But we can't do that if the process hangs, because the tail command would never run.

We may be able to trigger the tail using a sleep command, after the process has hung for 50 minutes?
(Our builds normally take 5-10 minutes.)

comment:7 Changed 5 days ago by teor

This also caused a failure in today's 0.2.9 backport rollup after merging to master:

comment:8 Changed 15 hours ago by teor

This bug caused our maint-0.4.0 cron job to fail today:

Note: See TracTickets for help on using tickets.