-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
[CI] Fix workflow inputs #47
Conversation
Specs are failing in Ubuntu for jeromegn/kilt. Why did you need to lower the macOS version? |
The
(Not that I have anything against betas! 🤗) |
@@ -99,6 +99,7 @@ function setup() { | |||
if [[ "$(crystal env CRYSTAL_VERSION)" =~ ^0\.|^1\.[0-8]\. ]]; then | |||
skiponwindows "Compiler bug in Crystal < 1.9" | |||
fi | |||
skiponwindows "Specs are failing" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the point of having the three lines above, if it's going to be skipped anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's different reasons for skipping. This documents that it's not expected to build with Crystal 1.8 and below. But after that it's (probably) up to the shard wether it works or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Answering myself: I assume the idea is that once we get the specs running OK in Windows, it still makes sense to filter them out with the version of Crystal being < 1.9
Fixup for #45
Adds the ability to specify the shards version.
Defaults all versions to
nightly
.Skips some tests that are failing on Windows.
Patches ameba for 1.9 compatibility.