5368e44a86
Several of the unit tests request that the peer emit more than one signal, but only handle one. The rest of the signals stay queued in the socket and will be delivered at the next test, causing it to fail often. This doesn't happen in the tests with the bus. There, we don't receive the extraneous signals due to AddMatch/ReceiveMatch on each signal individually and the synchronous nature of the emission (the signals have already been emitted by the next AddMatch and cannot match it). Task-number: QTBUG-42145 Change-Id: I743a0553074972042fca46b76db5d9e7b3209620 Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@digia.com> |
||
|---|---|---|
| .. | ||
| qdbusabstractadaptor | ||
| qdbusabstractinterface | ||
| qdbusconnection | ||
| qdbusconnection_no_bus | ||
| qdbuscontext | ||
| qdbusinterface | ||
| qdbuslocalcalls | ||
| qdbusmarshall | ||
| qdbusmetaobject | ||
| qdbusmetatype | ||
| qdbuspendingcall | ||
| qdbuspendingreply | ||
| qdbusreply | ||
| qdbusservicewatcher | ||
| qdbusthreading | ||
| qdbustype | ||
| qdbusxmlparser | ||
| dbus.pro | ||