Add CI testing - Githubissues

bit-hack / tack

Tack - The vector wrapper

0 stars 0 forks source link

Add CI testing #17

Open bit-hack opened 8 years ago

bit-hack commented 8 years ago

Now that we have a basic test suite we can think about adding some CI testing via TravisCI and AppVeyor. Questions:

Does AppVeyor support VS2015?
Should we be testing other compilers (Clang on Windows?)
Can we use QEmu-User and a cross compiler to test any future Neon implementation?
What other testing should we be doing?

kbenzie commented 8 years ago

This seems to say you can select between Visual Studio 2013 and 2015.
I've no idea what clang support on Windows is like, seems like a strange choice though.
Might be able to build QEmu as part of the build, will need to do more research.
As for other testing, I doing perf seems like something we should do but I'm not sure CI is the best place for that since the nodes will be sharing their resources and we will get unpredictable results.

bit-hack commented 8 years ago

I have made a simple travis yaml file here #18. I wonder if we can get more reproducible perf results by doing any profiling within a qemu instance? Also we should be able to apt install qemu user and system. The slow part will likely be downloading the images to run for qemu system. I have used the images from https://www.aurel32.net with much success before.