by CuteAlien » Mon Mar 26, 2012 9:32 pm
I've run tests today on different platforms, this are the current results (all debug, more tests fail in release):
Failing test results (24.3.2011) VS 2010 Windows 7 OS 64-bit compiling for 32-bit: 47, 49, 50, 51, 52, 53, 55, 57
Failing test results (26.3.2011) GCC Ubuntu compile 64-bit: 19, 22, 44, 47, 48, 49, 50, 51, 52, 54, 55, 56, 57, 58, 59, 60, 63, 64
Failing test results (26.3.2011) GCC Debian 32-bit: 47, 48, 49, 50, 51, 52, 54, 55, 56, 57, 58, 59, 60, 63, 64
Failing test results (26.3.2011) VS 2010 Windows XP 32-bit: 47, 49, 50, 51, 52, 53, 54, 55, 57,
So rather obvious we have to do better. But also maybe as info why other things currently have a hard time getting in... we shouldn't really add new stuff while our test-suite is broken as we don't see anymore then if new changes break even more things (and yeah, I also still add new stuff sometimes *sigh*, but I try to be careful not making the situation worse).
Anyone who can help there - for example figuring out which tests got broken in which svn revision would often help - is welcome (especially on 32-bit platforms, some tests probably never worked on 64-bit so far, I'm working mostly on those currently). If you want to help figuring out breaking revisions, you can do so easily - just run tests on your system, note which work (in tests.log) and then start checking out older revisions and compare until you have the revision where something changes. The test-suite is in folder "tests" (yeah.... hard to find *g*). And certainly if you can even find out _why_ a test breaks, what it's supposed to do and how it should be fixed... oh well I guess I'm just dreaming there ... but that sort of info would be great :-) (Note that in many cases tests probably just didn't get updated on engine-changes)
edit (2012/04/03): increased all testnumbers by one on "GCC Ubuntu compile 64-bit" as I noticed test 8 was outcommented to get it compiling. Should probably better replace numbers by names anyway (not now).