On Sat, Oct 21, 2017 at 8:16 PM, Thiago Macieira <thiago.macie...@intel.com> wrote: > > In this case, I'd just have the test harness kill the processes that > deadlocked and report the failure. >
Alright, I'll take it under advisement. The Qt Continuous Integration system has a timeout of 15 minutes for any > test, > except tst_QNetworkReply (that one is allowed to run for longer). That > way, we > don't depend on any internal state being consistent. Like you said, in the > case of a failing test, quite by definition the internal state of the > application is not what we expected it to be. > Ok, I'll have a look at that to see how it was implemented for the network classes, it should be pretty similar to what I need to do. Thanks for the input Thiago, much appreciated!
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
