Sergio Ahumada wrote: > On 11/20/2012 11:07 AM, Qt Continuous Integration System wrote: >> Autotest `tst_qdeclarativetextedit' failed :( > > This change (and tst_qwidget_window) has been failing a lot lately, so > .. who is responsible for ensuring that we don't block good changes > because of flaky tests ?
Good question! If you ask from me, module maintainer is responsible for fixing unstable auto tests on his/her own area. Of course maintainer can also delegate the fixing to some other person who can fix it on his behalf... Tuukka: Any comments? Or will we have dedicated QA people to follow-up for CI failures? CI team will of-course take care of CI failures which happen due to CI system but I think we will have quite limited capability to fix flaky auto tests etc. > I've being doing some work towards this .. but I am certainly not > responsible for it. Thanks for working on it! Br -- Janne Anttila Senior Architect - Digia, Qt Visit us on: http://qt.digia.com _______________________________________________ Ci-reports mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/ci-reports
