Elixir CI

Allow individual options to be disabled #497

Sign in to view logs

Triggered via pull request March 21, 2025 01:45

ZRothy1

opened #110

Semsee:feature/add-disabled-options

Status Failure

Total duration 1m 27s

Artifacts –

elixir.yml

on: pull_request

Matrix: build

Annotations

9 errors and 18 warnings

build (1.17, 27, true)

Process completed with exit code 8.

build (1.18, 27, true)

The operation was canceled.

build (1.18, 27, true)

The strategy configuration was canceled because "build._1_17_27_true" failed

build (1.16, 26)

The operation was canceled.

build (1.16, 26)

The strategy configuration was canceled because "build._1_17_27_true" failed

build (1.15, 26)

The operation was canceled.

build (1.15, 26)

The strategy configuration was canceled because "build._1_17_27_true" failed

build (1.14.1, 25)

The operation was canceled.

build (1.14.1, 25)

The strategy configuration was canceled because "build._1_17_27_true" failed

build (1.17, 27, true): lib/live_select/component.ex#L596

Function is too complex (cyclomatic complexity is 13, max is 12).

build (1.17, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.17, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.17, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.17, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.17, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.17, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.17, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.17, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.18, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.18, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.18, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.18, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.18, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.18, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.18, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.18, 27, true)

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

build (1.14.1, 25)

Logger.default_formatter/1 is undefined or private