AppVeyor builds seem to be broken

[striezel]

It looks like all more recent AppVeyor builds of Spine have failed. That way the CI build becomes meaningless, because it does not give an indication of whether the code actually builds properly or not. The last successful build on master was for commit 5fe615e, if I am not mistaken. That was approximately ten months ago. I guess it still builds in another environment, because there have been several releases of Spine in the meantime. This situation is especially frustrating when someone tries to contribute patches to the project.

Could someone please fix the AppVeyor CI so that is builds again on the master branch?
Alternatively, a GitHub Actions workflow will also be fine, if that is easier to do. Basically anything that is a working and publicly visible CI pipeline will be appreciated. :-)

Thanks.

[BonneCW]

Well, I took a look a while ago and it failed randomly in builds for no good reason. Maybe some timeout issue of AppVeyor. Might take a look once again in the future, but it's not a priority for me at the moment.