[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#930448: onioncircuits: autopkgtest seems to be unreliable

Control: severity -1 serious
Control: tags -1 + sid bullseye

On Wed, 12 Jun 2019 at 22:10:46 +0100, Simon McVittie wrote:
> The onioncircuits autopkgtest seems to fail occasionally, then succeed
> when retried.

This still seems to be happening, and is currently blocking glib2.0
from migrating (I've retried the test, but maintainers of dependencies
shouldn't have to do this: it doesn't scale for packages that many things
depend on, like GLib).

Latest failure:

autopkgtest [03:56:49]: test gui-test: [-----------------------
waiting for Tor to settle...
Creating logfile at /tmp/dogtail-testuser/logs/check-circuits_20200416-035710_debug ...
Warning: AT-SPI's desktop is visible but it has no children. Are you running any AT-SPI-aware applications?
[Errno 2] No such file or directory
/usr/lib/python3.8/subprocess.py:942: ResourceWarning: subprocess 3201 is still running
  _warn("subprocess %s is still running" % self.pid,
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/python3/dist-packages/stem/connection.py:348: ResourceWarning: unclosed <socket.socket fd=14, family=AddressFamily.AF_UNIX, type=SocketKind.SOCK_STREAM, proto=0>
  return None
ResourceWarning: Enable tracemalloc to get the object allocation traceback
ERROR: test_has_correct_circuits (__main__.TestOnionCircuitsGUI)
Traceback (most recent call last):
  File "debian/tests/check-circuits", line 72, in test_has_correct_circuits
    stemcircs = self._get_stem_circuits()
  File "debian/tests/check-circuits", line 45, in _get_stem_circuits
    with stem.connection.connect_socket_file() as controller:
AttributeError: __enter__

Ran 1 test in 1.028s

FAILED (errors=1)
autopkgtest [03:57:12]: test gui-test: -----------------------]

Full log: https://ci.debian.net/data/autopkgtest/testing/arm64/o/onioncircuits/5007791/log.gz

Please mark this test as flaky if it can't be made reliable.


Reply to: