Jasper van de Gronde wrote:

Bob Jamison wrote:

...

That was a good find, Adib! :)

Yes, adding test-stubs.cpp to the 'excludes' list does fix the build.

But someone needs to look at test-stubs.cpp and get it back into sync with the current fields in Preferences. Or take it out, I guess.

Perhaps the person who actually broke the tests? I know it can be a pain, but people (and frankly that includes me) really should run these tests more often. At the moment the tests even CRASH for me...

Correction, after a build clean it doesn't crash anymore. Currently 14 out of 160 tests fail on my system.

This makes me wonder if we can't set up some machine to regularly do these tests (and the rendering tests as well while we're at it). Running all the tests once a day (the unit tests take about a minute, excluding build time) would already be an enormous improvement.

If we want it a little fancier it could try and pinpoint the exact revisions which caused the problem and possibly even notify the developers mailing list (and/or the individual developers involved).