Skip to content
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

Disable specs using GB2312 encoding on musl (fixes #3976) #5867

Closed
wants to merge 1 commit into from

Conversation

jirutka
Copy link
Contributor

@jirutka jirutka commented Mar 26, 2018

Musl libc does not support GB2312 encoding.

Musl libc does not support GB2312 encoding.

Fixes crystal-lang#3976
@jirutka
Copy link
Contributor Author

jirutka commented Mar 26, 2018

With this patch and #5866 all specs pass on x86_64 and aarch64 Alpine Linux* (musl)! 🎉

* when building with OpenSSL instead of LibreSSL

@jhass
Copy link
Member

jhass commented Mar 26, 2018

Not all of these seem to be specifically about this encoding but rather any encoding that's not UTF. So we probably should switch those to a more supported encoding or at least add versions that work for musl, instead of just disabling them

@ysbaddaden
Copy link
Contributor

Yes, let's keep the failing specs as a reminder that we should change them to use a more broadly supported non-UTF encoding.

@straight-shoota
Copy link
Member

Could wrap them in pending to express the TODO-meaning.

@RX14
Copy link
Contributor

RX14 commented Mar 26, 2018

There have been pending specs in this repo that have been pending since before I even knew what crystal was. I think it's unlikely that pending specs will get noticed.

@jirutka
Copy link
Contributor Author

jirutka commented Mar 26, 2018

And since you don’t run tests against musl on CI, it’s unlikely that anyone will notice that they are broken… :/

@straight-shoota
Copy link
Member

Sure, but the difference is in the semantics: failing specs means it is broken and pending means, this needs to be implemented but it's mostly usable.

@RX14
Copy link
Contributor

RX14 commented Mar 26, 2018

Maybe ISO-8859-1 is supported in musl?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants