Skip to content
Elixir CI

Ensure the remote control node and server use the same Elixir executable #2515

Sign in to view logs

Ensure the remote control node and server use the same Elixir executable

Ensure the remote control node and server use the same Elixir executable #2515

Triggered via pull request July 19, 2024 16:59
@zachallaunzachallaun
synchronize #795
za-deduplicate-vm-detection
Status Success
Total duration 10m 10s
Artifacts –

elixir.yml

on: pull_request
Static analysis
42s
Static analysis
Run Dialyzer
9m 57s
Run Dialyzer
Integration tests
2m 58s
Integration tests
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 109 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/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
Static analysis
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test on OTP 25 / Elixir 1.16
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test on OTP 25 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.16
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test on OTP 26 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.16
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.15.6
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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 25 / Elixir 1.14
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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 25 / Elixir 1.17
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test on OTP 25 / Elixir 1.17
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 25 / Elixir 1.17
1..-2 has a default step of -1, please write 1..-2//-1 instead
Test on OTP 25 / Elixir 1.17
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 25 / Elixir 1.17
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
Test on OTP 25 / Elixir 1.17
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
Test on OTP 25 / Elixir 1.17
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 25 / Elixir 1.17
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 25 / Elixir 1.17
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 25 / Elixir 1.17
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 25 / Elixir 1.17
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 25 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 25 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test on OTP 26 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 26 / Elixir 1.17
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.17
1..-2 has a default step of -1, please write 1..-2//-1 instead
Test on OTP 26 / Elixir 1.17
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.17
_.._ 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.17
_.._ 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.17
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.17
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.17
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.17
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.17
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.17
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test on OTP 27 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 27 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 27 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 27 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 27 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 27 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 27 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 27 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 27 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 27 / Elixir 1.17
negative steps are not supported in String.slice/2, pass 1..-2//1 instead
Test on OTP 27 / Elixir 1.17
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.17
1..-2 has a default step of -1, please write 1..-2//-1 instead
Test on OTP 27 / Elixir 1.17
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.17
_.._ 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.17
_.._ 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.17
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.17
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.17
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.17
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.17
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
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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