Thiago Macieira wrote:
> > It means one of: > a) your system is swapping so hard that everything takes 1000x more than it > should (like the Qt CI system) Swapping or something else that has a similar effect to disk access times, yeah, that's about what happened. > Is the state QProcess::NotRunning or QProcess::Starting ? From reading the > source code in qprocess_unix.cpp, the error QProcess::Timedout can only happen > if poll(2) really did time out. I'd have to print the state in my warning message, the 2 times I got a timeout today the application crashed and I didn't feel like doing much post-mortem debugging on a swamped system. FWIW there's a full backtrace here: https://bugs.kde.org/show_bug.cgi?id=377489#c1 R _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
