CI

[Lewiscowles1986]

Hello. Thanks for taking the time to write this and make it public. I came in via #42 but can see you use a unit testing framework.

I've been trying to generate coverage, both by forking your repo and running your travis.yml there are errors. I wasn't sure if you knew about them, including but not limited to commands for executable files that are not installed, passing a token that can just be set via travis settings.

I'm currently trying to fix these problems, but it seems C++ coverage is harder to generate than the same in Java, C# or scripting language.

[Lewiscowles1986]

https://github.com/CODESIGN2/silicon/tree/coverage-works/ has the dockerfile build tests that generate coverage using lcov. There still seems to be some problem (it's reporting 0.0%) but it does so based upon the silicon source tree so as soon as I've worked out what has gone wrong there I have the coveralls system receiving that data.

[matt-42]

Just for info I did some work some time ago to make the travis.yml work again: https://travis-ci.org/matt-42/silicon
I had to disable all compilers but clang-5.0 and also the optional test.

[Lewiscowles1986]

That is the vein of work I've picked up. Thanks for that. So-far the largest problem seems to be differing CLI API's between versions of needed software. I think once it's built successfully matrix, tests only built for clang builds and sending coverage, then the rest should be easy to turn back on.