-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Update test suite for Erlang 19 #4851
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
Comments
Thanks for reporting. We are aware of those failures and we have reported On Wednesday, June 22, 2016, Peuh [email protected] wrote:
José Valim |
No problem. Thanks for the awesome job on elixir. Just starting with it but I like it a lot already. Considering those failed tests, should I downgrade erlang to v18 and recompile or it will work anyway? It's a dev environment, not production. |
@peuh those bugs are all related to typespecs and it should not affect your code in anyway. You will just get more warnings than necessary if you are using a tool called Btw, this is up for grabs. Unfortunately we can't solve the dialyzer issue, so it means we should not run that particular test for Erlang 19. The issues related to callback means we need to fetch the callback information differently (by traversing the beam abstract syntax tree and collecting callbacks). Both solutions should work fine on Erlang 18 too. |
Thanks for the update @josevalim. |
Grabbing this. |
After compiling elixir from source, 5 tests fail. Also the compilation emits a few warnings.
I have the same result whether I use master or tag/1.3
Environment
Debian Stretch (and some bit of unstable)
Erlang (installed using the standard .deb provided on erlang official website):
Current behavior
Here is the console output from
make clean test
Expected behavior
No test failures :-)
The text was updated successfully, but these errors were encountered: