Elixir CI

Allow individual options to be disabled #500

Sign in to view logs

Triggered via pull request March 21, 2025 14:38

ZRothy1

synchronize #110

Semsee:feature/add-disabled-options

Status Failure

Total duration 1m 18s

Artifacts –

elixir.yml

on: pull_request

Matrix: build

Annotations

11 errors and 17 warnings

build (1.16, 26)

Process completed with exit code 1.

build (1.15, 26)

Process completed with exit code 1.

build (1.15, 26)

** (SyntaxError) lib/live_select/component.ex:638:3: unexpected reserved word: end

build (1.15, 26)

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

build (1.14.1, 25)

Process completed with exit code 1.

build (1.14.1, 25)

** (SyntaxError) lib/live_select/component.ex:638:3: unexpected reserved word: end

build (1.14.1, 25)

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

build (1.17, 27, true)

The operation was canceled.

build (1.17, 27, true)

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

build (1.18, 27, true)

The operation was canceled.

build (1.18, 27, true)

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

build (1.14.1, 25)

Logger.default_formatter/1 is undefined or private

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