20642 – jingle/test-incoming-call-reject.py occasionally fails

Bug 20642 - jingle/test-incoming-call-reject.py occasionally fails

Summary: jingle/test-incoming-call-reject.py occasionally fails

Status:	RESOLVED FIXED

Alias:	None

Product:	Telepathy
Classification:	Unclassified
Component:	gabble (show other bugs)
Version:	unspecified
Hardware:	Other All

Importance:	medium normal
Assignee:	Telepathy bugs list
QA Contact:	Telepathy bugs list

URL:
Whiteboard:
Keywords:

Depends on:	20885
Blocks:
	Show dependency tree / graph

Reported:	2009-03-13 04:24 UTC by Guillaume Desmottes
Modified:	2009-04-08 10:55 UTC (History)
CC List:	0 users

See Also:
i915 platform:
i915 features:

Attachments
test log (15.99 KB, text/x-log) 2009-03-13 04:44 UTC, Guillaume Desmottes	Details
gabble log (29.61 KB, text/x-log) 2009-03-13 04:45 UTC, Guillaume Desmottes	Details
View All

Description Guillaume Desmottes 2009-03-13 04:24:37 UTC

Got this error when running "make check". Don't have logs unfortunately.

Traceback (most recent call last):
  File "/home/cassidy/dev/telepathy-gabble/telepathy-gabble-0.7.22.1/tests/twisted/gabbletest.py", line 388, in exec_test_deferred
    f(queue, bus, conn, stream)
  File "../../../tests/twisted/jingle/test-incoming-call-reject.py", line 81, in test
    assert iq.query.name == 'jingle'
AttributeError: Event instance has no attribute 'query'

Comment 1 Guillaume Desmottes 2009-03-13 04:36:10 UTC

Oh sorry, my branch wasn't sycned on master. Could have been fixed recently.

Comment 2 Guillaume Desmottes 2009-03-13 04:42:20 UTC

Just got this problem with master

Comment 3 Guillaume Desmottes 2009-03-13 04:44:09 UTC

Created attachment 23830 [details]
test log

Comment 4 Guillaume Desmottes 2009-03-13 04:45:03 UTC

Created attachment 23831 [details]
gabble log

Comment 5 Will Thompson 2009-03-26 10:52:00 UTC

I fixed this en passant in the branch awaiting review over at #20885.

Comment 6 Will Thompson 2009-04-08 10:55:57 UTC

Fixed in 0.7.25.

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.