QEventLoop::quit fails with nested calls to processEvents when using the unix event dispatcher

When the unix event dispatcher is used, a call to QEventLoop::quit does not have the desired effect when immediately followed by some sort of nested call to processEvents, for example through a nested eventloop, QTest::wait, or similar. The reason appears to be that the second processEvents resets the interrupt flag previously set by quit(), since that is unconditionally done at the start of processEvents(), thereby aborting the quit. Testcase that reproduces this failure attached. This is a reduced test case from a failing (on OSX) unit test in KDE's kdelibs, which passes on linux, suggesting that the glib event loop is unaffected.