-
Notifications
You must be signed in to change notification settings - Fork 65
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
Move to updated Elixir and Erlang versions #228
Conversation
Thanks! Seems like we have some legit memory failures and I think we might need to exclude 1.4/1.5 for OTP 21. |
Yeah memory measurements somehow break... the old scenario from @michalmuskala (that we gladly tested) breaks and so does some simple stuff like: It gets exactly the same heap information before/after... which makes no sense unless this scenario is now optimized/inlined as well:
(also no memory collected) |
Still pushed my upgrade to remove the unfitting builds from the built matrix... leaving this alone again now because the 3 failures seem hard to figure out :( |
In case anyone sees this and thinks wtf they aren't working on this... we are but it's hard and we're scratching all our heads. |
Ok the memory measurement problems exist whether we merge this or not... I think we'll skip the problematic tests on OTP 21 until we merge them :) |
* Move to updated Elixir and Erlang versions * Exclude unsupported elixir<->otp configurations * exclude problematic tests for now, filed #234 to follow up * Old OTP or elixir versions are not yet ready for the mighty ł
* Move to updated Elixir and Erlang versions * Exclude unsupported elixir<->otp configurations * exclude problematic tests for now, filed #234 to follow up * Old OTP or elixir versions are not yet ready for the mighty ł
No description provided.