On Thu, Nov 8, 2018 at 8:15 PM Ben Cooksley <bcooks...@kde.org> wrote: > > On Sat, Nov 3, 2018 at 4:41 PM Ben Cooksley <bcooks...@kde.org> wrote: > > > > Hi all, > > > > Following commits made to Frameworks somewhere in the October 21 to > > October 28 time frame, the unit tests of Konsole on the CI system have > > started to hang following completion. > > > > This hang is occurring due to a behaviour of CTest, where it will wait > > (indefinitely) following the conclusion of a test for processes > > spawned by that test to exit. > > > > Previously, the "konsole --separate" process launched by Konsole's > > dbus unit test would exit normally, however following the changes in > > Frameworks it now hangs and does not exit as expected. > > > > This is causing quite a bit of trouble as these builds require manual > > Sysadmin intervention in order to have the jobs complete successfully. > > > > Could someone take a look into this regression please? > > > > Regretfully it isn't possible to run GDB within the CI system > > environment (Docker drops CAP_SYS_PTRACE) so i'm unable to get a > > backtrace out of Konsole to find where it is stuck. > > Ping? > > Anyone got any idea why this behaviour has regressed?
The complete lack of response to this issue (and any mail to this mailing list i've noticed, I highly suspect everyone just filters it into a corner in their mail client and doesn't read it at all) is really disappointing. Given that Kurt has disabled the test within Konsole this doesn't have any urgency anymore. None the less though the fact a regression with hang-on-application-close implications was detected by the CI system and then completely ignored by those who broke it brings up other concerns, and essentially means the CI system is given no regard by the Frameworks developers. As a consequence i'll be terminating CI and Phabricator notification mails to the Frameworks mailing list, effective immediately. > > > > > Thanks, > > Ben > > Regards, > Ben Regards, Ben Cooksley KDE Sysadmin