Build and test on additional platforms

[aahlenst]

We're currently only building and running the test suite on Linux. We should at least include macOS and, if possible, Windows.

Question is what service we want to use. Travis CI has macOS workers, their Windows support is spotty at best (only Python 2.7 preinstalled). So either we hook up public or private AppVeyor. @ynop, what do you think?

[ynop]

Yes, good point. I think public AppVeyor would be a good choice.

[ynop]

Or is there any difference to the private AppVeyor? Can "outsiders" see the build reports?

[aahlenst]

Doing it on Travis CI it's a bit a mess: https://docs.travis-ci.com/user/languages/python/#running-python-tests-on-multiple-operating-systems

Not sure whether it makes sense to investigate other options like Circle CI or GitHub Actions.

Or is there any difference to the private AppVeyor?

We can use as many resources as we want without paying a dime. Plus we can make the build experience more pleasant, for example by pre-installing pyenv on the macOS workers.

Can "outsiders" see the build reports?

Should be doable. Never tried before, though.

[aahlenst]

Because of #109, in my opinion we should run pytest bench during CI. Unfortunately, Travis CI cannot handle it: https://travis-ci.com/github/ynop/audiomate/builds/152818414

Either it does not have enough memory or it stops the build because some benchmarks take too much time.

[ynop]

Would definitely make sense to run benchmarks as well. We could try it on our AppVeyor instance, as soon as we find time to set it up.