You probably want to turn on AppVeyor for ECOS.jl for testing purposes, and make sure to either create a new Windows binary and/or copy the existing version number for the sake of the Windows binary next time a Linux version bump is desired.
Coverage remained the same when pulling a39519218b1a65ed8bf81e90a4f0f87d6b3970e3 on tkelman:patch-1 into b7e4a20cf40693d35452b24a0d73789d19bd0d76 on JuliaOpt:master.
This tests cleanly on both Win32 https://ci.appveyor.com/project/tkelman/ecos-jl/build/1.0.7/job/5sw93vkt40uqnxsx and Win64 https://ci.appveyor.com/project/tkelman/ecos-jl/build/1.0.7/job/kxqfbv6jgyj14c6i
You can generate these automatically on AppVeyor from a fork of the ECOS repository with this yml: https://github.com/tkelman/ecos/blob/0e53f6e53f38d44b9d8299d6a8faaec7f3dcdf69/appveyor.yml however that's not ideal because it results in a new SHA that doesn't exist upstream.
You probably want to turn on AppVeyor for ECOS.jl for testing purposes, and make sure to either create a new Windows binary and/or copy the existing version number for the sake of the Windows binary next time a Linux version bump is desired.