Run tests in CI

[cjmayo]

Needs fixing for Windows.

Don't know if this is change is wanted but I was interested to see because when I run locally I get:

 11 - OndselSolver.Gears (Subprocess aborted)
 12 - OndselSolver.anglejoint (Subprocess aborted)
 13 - OndselSolver.constvel (Subprocess aborted)
 14 - OndselSolver.rackscrew (Subprocess aborted)
 15 - OndselSolver.planarbug (Subprocess aborted)
 18 - OndselSolver.piston (Subprocess aborted)

[chennes]

I always think it's a good idea to run your test suite as part of your CI, so I think this is a clear improvement.

[PaddleStroke]

@chennes any idea what the failing checks means? Is it still safe to merge?

[chennes]

I probably wouldn't merge it until you've run the tests locally in a debugger and figured out what is segfaulting. The fact that it's happening on all of the CI platforms generally indicates that the problem is real.

[cjmayo]

Apparently it is caused by C++ class name mangling:

https://github.com/gentoo/gentoo/blob/1896fac74ffa1cdb67fd9c9d3d85a618096c5d40/sci-libs/ondselsolver/files/ondselsolver-1.0.1-properly-demangle-typenames.patch