Skip to content

Support Elixir 1.18 #2621

Support Elixir 1.18

Support Elixir 1.18 #2621

Triggered via pull request December 28, 2024 00:50
@scohenscohen
synchronize #849
support_1_18
Status Success
Total duration 10m 8s
Artifacts

elixir.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 73 warnings
Test on OTP 25 / Elixir 1.15.6
** (SyntaxError) lib/parse_errors.ex:15:3: unexpected reserved word: end
Test on OTP 25 / Elixir 1.15.6
** (SyntaxError) lib/compilation_errors.ex:4:3: unexpected reserved word: end
Test on OTP 26 / Elixir 1.15.6
** (SyntaxError) lib/parse_errors.ex:15:3: unexpected reserved word: end
Test on OTP 26 / Elixir 1.15.6
** (SyntaxError) lib/compilation_errors.ex:4:3: unexpected reserved word: end
Static analysis
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Integration tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 27 / Elixir 1.18.1
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 27 / Elixir 1.18.1
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
Test on OTP 27 / Elixir 1.18.1
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
Test on OTP 27 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 27 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 27 / Elixir 1.18.1
min..min inside match is deprecated, you must always match on the step: min..min//var or min..min//_ if you want to ignore it
Test on OTP 27 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 27 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 27 / Elixir 1.18.1
min..min inside match is deprecated, you must always match on the step: min..min//var or min..min//_ if you want to ignore it
Test on OTP 27 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 27 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 27 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 27 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 27 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 27 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 27 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 27 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 27 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 27 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 27 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 27 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.17
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 25 / Elixir 1.16
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 25 / Elixir 1.17
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 27 / Elixir 1.17
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 25 / Elixir 1.15.6
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 25 / Elixir 1.15.6
variable "b" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.15.6
variable "a" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 26 / Elixir 1.15.6
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 26 / Elixir 1.15.6
variable "b" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 26 / Elixir 1.15.6
variable "a" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 26 / Elixir 1.16
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 25 / Elixir 1.14
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 25 / Elixir 1.14
variable "b" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.14
variable "a" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.14: config/config.exs#L4
variable "f" does not exist and is being expanded to "f()", please use parentheses to remove the ambiguity or change the variable name
Test on OTP 25 / Elixir 1.13
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 25 / Elixir 1.13
variable "entry" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.13
variable "entry" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.13
variable "remaining" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.13
variable "first" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.13
variable "second" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.13
variable "found" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.13
variable "b" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.13
variable "a" is unused (if the variable is not meant to be used, prefix it with an underscore)
Test on OTP 25 / Elixir 1.13: config/config.exs#L4
variable "f" does not exist and is being expanded to "f()", please use parentheses to remove the ambiguity or change the variable name
Test on OTP 26 / Elixir 1.18.1
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test on OTP 26 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.18.1
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
Test on OTP 26 / Elixir 1.18.1
Failed to save: Cache service responded with 429 during commit cache.
Test on OTP 26 / Elixir 1.18.1
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
Test on OTP 26 / Elixir 1.18.1
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
Test on OTP 26 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 26 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 26 / Elixir 1.18.1
min..min inside match is deprecated, you must always match on the step: min..min//var or min..min//_ if you want to ignore it
Test on OTP 26 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 26 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 26 / Elixir 1.18.1
min..min inside match is deprecated, you must always match on the step: min..min//var or min..min//_ if you want to ignore it
Test on OTP 26 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Test on OTP 26 / Elixir 1.18.1
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Run Dialyzer
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run Dialyzer
use Bitwise is deprecated. import Bitwise instead
Run Dialyzer
Supervisor.Spec.worker/2 is deprecated. Use the new child specifications outlined in the Supervisor module instead