summaryrefslogtreecommitdiffstats
path: root/tests/benchmarks/dbus/qdbusperformance/tst_qdbusperformance.cpp
diff options
context:
space:
mode:
authorThiago Macieira <thiago.macieira@intel.com>2014-12-11 15:51:01 -0800
committerThiago Macieira <thiago.macieira@intel.com>2014-12-20 07:37:01 +0100
commit3148d0c7b403af1bd74a2082cdde61e6974b38c1 (patch)
tree1a86e162c0a881936e440263e412d894e4044a54 /tests/benchmarks/dbus/qdbusperformance/tst_qdbusperformance.cpp
parent91fe8129fa54847b8d4146672d561349633aea79 (diff)
Don't kill the subprocess in tst_qdbusabstractinterface
Rohan was right in e88f9a92b7ab05ea9bc25083de7dee1b67dd673e to stabilize the test and reset the state, but killing the subprocess is overkill. All we need is to reset the state in both applications, which includes disconnecting and reconnecting to the peer, to discard any sent but not yet received messages. Change-Id: Ie01392e6e63bd70ef8345217d3fc641ed63c7aba Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
Diffstat (limited to 'tests/benchmarks/dbus/qdbusperformance/tst_qdbusperformance.cpp')
0 files changed, 0 insertions, 0 deletions