Allow a custom timeout for wait_for_bus_object()

Bug #1218318 reported by James Henstridge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-dbusmock
Fix Released
Wishlist
Unassigned

Bug Description

It would be nice if DBusTestCase.wait_for_bus_object() let the caller specify an alternative timeout. I've had some test cases fail when I am fairly certain it is just a case of the service I'm waiting on taking too long to connect to the bus.

When I know that a service takes a while to start up, it would be nice if I could specify a more forgiving timeout.

Revision history for this message
Martin Pitt (pitti) wrote :

Ah, this method was actually intended to be used internally only, for waiting for the mock proxy to arrive (which should really work within 5 s). But I don't mind adding a timeout argument.

Changed in python-dbusmock:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :

Fixed in trunk r136.

Changed in python-dbusmock:
status: Triaged → Fix Committed
Revision history for this message
James Henstridge (jamesh) wrote :

Thanks.

While I realise that the mock proxy is the main focus of the library, the DBusTestCase class is also useful to build fixtures to drive real code that uses D-Bus in an isolated fashion (which is what my use case was).

Revision history for this message
Martin Pitt (pitti) wrote :

This was released a while ago in 0.7.2.

Changed in python-dbusmock:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.