On Mon, Nov 9, 2015 at 10:26 AM, Albert Astals Cid <aa...@kde.org> wrote: > El Saturday 07 November 2015, a les 10:36:18, David Faure va escriure: >> On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: >> > Hi all, >> > >> > It appears the test running with the binary name of "threadtest" in >> > kio has a grave bug which can lead to it entering into an infinite >> > loop. >> > >> > This was consuming virtually the entire resources of one builder with >> > old hung processes, and the whole core of another builder - >> > drastically limiting the capabilities of the CI system (even though >> > KIO was not being built at the time). >> > >> > Can someone please investigate? Manual intervention (with kill -9) is >> > needed to remove these hung processes. >> >> It of course works fine on my own machine. >> >> And I just tried running it on LinuxNode2, in >> ~/builds/kio/stable-kf5-qt5/build/autotests (after sourcing ~/kio.env which >> I just generated), and it ran fine (multiple times). >> >> Any suggestion on how / where to hit the issue? > > I too have serious problems being able to reproduce the same results on the > build nodes than CI has :( > > I guess we're most probably missing some step (e.g. kdelibs failing test > always work when i try to reproduce it, rocs compiles fine, etc)
Albert, did you try with the kf5-qt5 or stable-kf5-qt5 branch group? It seems this is a Qt regression (and the version differs). > > Cheers, > Albert Regards, Ben > _______________________________________________ > Kde-frameworks-devel mailing list > Kde-frameworks-devel@kde.org > https://mail.kde.org/mailman/listinfo/kde-frameworks-devel _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
