-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop AppVeyor #422
Drop AppVeyor #422
Conversation
The point of the AppVeyor build is to test on Windows. If we remove AppVeyor, we must add a Windows build to the GitHub Actions CI. |
GitHub has Windows machines available for running Actions, with matrix it is relatively easy to setup, I will add it to this PR. |
The Windows build doesn't seem to test anything. It completed in 1 minute without doing much of anything. By comparison, the Linux build takes more than 15 minutes. |
Really strange. Posted in community about it - https://git.luolix.topmunity/t/windows-runner-not-executing-sbt-commands/250507. |
Note that olafurpg/setup-scala action is effectively deprecated. It might not be doing the right things. |
@armanbilge You were right, many thanks! One test does fail, and the runner seems quite slow, but the same test fails on my Windows machine too. AppVeyor tests run on older WIndows Server version, so that must be related. Will look into that next. |
Looks nasty:
https://github.com/scalacenter/scalajs-bundler/runs/6439309039?check_suite_focus=true#step:8:694 |
Looks related to scala/bug#11955. |
@sjrd Does this look mergeable to you? |
LGTM. Could you squash everything in a single commit with a clean commit message, please? Please also explain the change of Scala version in the test. |
@sjrd Done! |
With CI being already migrated to GitHub Actions, keeping AppVeyor seems unnecessary. Less CI scripts to maintain. Since GitHub Actions require approval for first time contributors and AppVeyor did not, maybe it would be good to reconsider loosening this rule for GitHub Actions in this repository.