Bug 20635 - tube-related tests sporadically fail
Summary: tube-related tests sporadically fail
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
Depends on:
Reported: 2009-03-12 13:04 UTC by Will Thompson
Modified: 2019-12-03 19:18 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

accept-private-dbus-tube failing (105.11 KB, text/x-log)
2009-03-12 13:04 UTC, Will Thompson
accept-private-dbus-tube failing in a different way! (75.76 KB, text/x-log)
2009-03-12 13:13 UTC, Will Thompson
gabble log from the second attached test failure (101.84 KB, text/x-log)
2009-03-12 13:17 UTC, Will Thompson
accept-private-dbus-tube race test log (1.64 KB, text/plain)
2010-01-25 21:07 UTC, Mike Ruprecht

Description Will Thompson 2009-03-12 13:04:37 UTC
Created attachment 23807 [details]
accept-private-dbus-tube failing

With current Gabble master, some of the tube tests sporadically fail. I have attached accept-private-dbus-tube failing: it appears never to get s5b-connected.

I'll also attach the Gabble log but it's for the entire test suite run :(
Comment 1 Will Thompson 2009-03-12 13:13:59 UTC
Created attachment 23808 [details]
accept-private-dbus-tube failing in a different way!

Bugzilla wouldn't let me attach the full Gabble log. So I ran just this test in a loop, until it failed again (but this time it fails differently!). New test log attached; gabble log to follow.
Comment 2 Will Thompson 2009-03-12 13:17:23 UTC
Created attachment 23809 [details]
gabble log from the second attached test failure
Comment 3 Guillaume Desmottes 2009-03-13 03:07:29 UTC
First log is a failing in offer-private-stream-tube.py not accept-private-dbus-tube.
Looking at the code it doesn't seem to be a race so for some reason Gabble failed to connect to your SOCKS5 socket.
Comment 4 Guillaume Desmottes 2009-03-13 03:54:25 UTC
I've been able to reproduce the second issue (accept-private-dbus-tube.py). It seems that the s5b-connected is not fired but, according to Gabble log, Gabble properly connected to the socket. I have no idea why.
Comment 5 Dafydd Harries 2009-09-28 15:56:12 UTC
I wonder if this has the same cause as #22022. Sometimes the tests also time out on waiting for TransferredBytes to change.
Comment 6 Mike Ruprecht 2010-01-25 21:07:51 UTC
Created attachment 32819 [details]
accept-private-dbus-tube race test log

In the accept-private-dbus-tube test, the code waits for the s5b-connected and AcceptDBusTube (through the expected_before argument) events with expect_many. It then expects to receive the s5b-data-received event with the auth request.

What's happening for me is it receives the s5b-connected event, but before it gets the AcceptDBusTube event, it receives the s5b-data-received event. The s5b-data-received event goes unhandled. Then after the AcceptDBusTube event is received, when it gets to where it expects the s5b-data-received event, it times out.

Attached is the excerpt from the test log illustrating this.
Comment 7 Pacho Ramos 2010-10-02 09:46:51 UTC
With 0.10.2 I am only suffering problems reported in bug 30565
Comment 8 GitLab Migration User 2019-12-03 19:18:42 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/23.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.