Test execution for all of PIM

[David Faure]

On lundi 25 février 2019 10:18:43 CET Ben Cooksley wrote:
> On Mon, Feb 25, 2019 at 10:54 AM David Faure <faure at kde.org> wrote:
> > Hi Ben,
> 
> Hi David,
> 
> > at this point I don't think that a timer-for-quitting would help, because
> > the one bug I was able to reproduce locally was leading rather to a
> > deadlock [deep within mariadb, details attached], so the event loop
> > wouldn't be running anymore -- and a timer would be useless.
> > 
> > In any case, https://phabricator.kde.org/D18888 fixes / works around that
> > problem (by removing a data race).
> 
> Interesting. That would certainly align with what we've seen.
> 
> > So I'd like to see if this fixes the CI issue, or if there are more
> > problems. Can you re-enable test execution for akonadi (or all of PIM)
> > and ping me if you again see the need to kill stuck processes? If
> > possible I'd like to debug those stuck processes before they get
> > killed...
> 
> I've now re-enabled it. Historically it's only shown up every couple
> of runs so we may need to wait a bit for it to show up.
> If it does show up i'll let you know (we can safely leave a Linux
> builder stuck as those are dynamically provisioned - if it blocks
> Windows or FreeBSD though we'll have to unstick that as there are only
> a couple of those)

That's fine, I'm much more at ease debugging on Linux, anyway ;-)

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5