Raul Ferreira

Any updates? Worst case scenario, you could just re-run the CI pipeline.

This might help https://www.appveyor.com/docs/deployment/github/

Please clean caches and re-run CI. The remaining failures are warnings being treated as errors, I think.

Ok, ignoring the warnings still doesn't make all tests pass. But everything else seems to be working.

Do you want me to do a rebase and include only the appveyor changes?

Here's [something](https://ci.appveyor.com/project/Zialus/compute/builds/21241647) you might be interested in checking out. Is that behavior on the Ubuntu images expected? I'll open a PR with a windows only appveyor config.

I have checked it out in the past, but it was still pretty green. Here's something I just cobbled up together https://travis-ci.com/Zialus/compute/builds/95828633

I might try that tomorrow. Is there a reason appveyor isn't getting triggered with the new commits?

Just to be clear, for this new PR should I branch of from `develop` instead of `master`(unlike what's stated in contribute.md)?

@jszuppe could you help out with the caching of boost on windows? I'm not sure what to do about the OpenCL part though. It's working fine on appveyor. https://ci.appveyor.com/project/Zialus/compute/builds/21322560