-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fix specs on win32 #8670
Fix specs on win32 #8670
Conversation
@@ -106,7 +106,7 @@ describe "#print Float64" do | |||
test_pair 5.5626846462680035e-309, "5.562684646268003e-309" | |||
end | |||
|
|||
it "falure case" do | |||
pending_win32 "failure case" do |
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.
Why is this broken?
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.
I have no idea. It returns a different result. Maybe that's expected? IDK. Needs investigation into the win32 libs.
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 seems there is something fundamentally broken with floating point numbers on win32:
"%f" % 1.0 # => "0.000000"
ba70814
to
f5498ff
Compare
We need to sort the expected results in order to make the specs pass on Windows because `foo\` and `foo/` compare differently with `foo2`.
f5498ff
to
1b6514e
Compare
Rebased to squash fixups. |
1b6514e
to
3f0feea
Compare
This either fixes or disables specs that don't succeed on win32.
With this and #8668
win32_std_spec.cr
should be all green 👍