Skip to content

Change get_range/1 to allow returning nil and add syntax corpus #391

Change get_range/1 to allow returning nil and add syntax corpus

Change get_range/1 to allow returning nil and add syntax corpus #391

Triggered via pull request September 11, 2023 15:42
Status Failure
Total duration 58s
Artifacts

main.yml

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

Annotations

8 errors and 10 warnings
ci (1.10.4, 21.3, true): test/range_test.exs#L727
test get_range/1 should never raise (SourcerorTest.RangeTest)
ci (1.10.4, 21.3, true)
Process completed with exit code 1.
ci (1.12.3, 24.3, true): test/range_test.exs#L727
test get_range/1 should never raise (SourcerorTest.RangeTest)
ci (1.12.3, 24.3, true)
The operation was canceled.
ci (1.13.4, 24.3)
The operation was canceled.
ci (1.14.3, 25.2)
The operation was canceled.
ci (1.13.4, 25.0.2, true, true, true, true)
The operation was canceled.
ci (1.11.4, 23.2, true)
The operation was canceled.
ci (1.10.4, 21.3, true)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ci (1.10.4, 21.3, true)
the following fields are unknown when raising SyntaxError: [column: 5]. Please make sure to only give known fields when raising or redefine SyntaxError.exception/1 to discard unknown fields. Future Elixir versions will raise on unknown fields given to raise/2
ci (1.10.4, 21.3, true)
the following fields are unknown when raising TokenMissingError: [column: 7]. Please make sure to only give known fields when raising or redefine TokenMissingError.exception/1 to discard unknown fields. Future Elixir versions will raise on unknown fields given to raise/2
ci (1.12.3, 24.3, true)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ci (1.13.4, 24.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ci (1.14.3, 25.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ci (1.14.3, 25.2)
Application.get_env/3 is discouraged in the module body, use Application.compile_env/3 instead
ci (1.14.3, 25.2)
use Bitwise is deprecated. import Bitwise instead
ci (1.13.4, 25.0.2, true, true, true, true)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ci (1.11.4, 23.2, true)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/