Keeping CI green

[Martin Gräßlin]

On Friday 23 May 2014 19:53:38 Albert Astals Cid wrote:
> El Divendres, 23 de maig de 2014, a les 07:19:59, Martin Gräßlin va 
escriure:
> > On Thursday 22 May 2014 21:08:05 Alex Merry wrote:
> > > There are currently four frameworks that are yellow (for between 6 hours
> > > and 8 days). kdelibs4support has had 3 commits (not counting those by
> > > scripty) since it broke that have done nothing to fix the issue.
> > 
> > One of the failing frameworks is KWindowSystem, sometimes it succeeds,
> > sometimes it doesn't.
> > 
> > I would love to get this more stable, but at the moment my solution is to
> > ping Ben to run the build again (as done in build #66 which fixed without
> > changes).
> 
> Can the test be made more stable?

I currently have no idea why the test is failing in a non-deterministic way. 
If I run it locally with a similar setup (Xvfb started with same args as on CI 
system and openbox) the test never fails. This makes it very difficult to 
investigate what is the problem in the first place.

At the moment I think it's still more useful to have the test, than to disable 
it. I just need to be faster in noticing that the test failed again.

Cheers
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140523/e3b68dc2/attachment.sig>