Skip to content
Build

Merge raisesCondition() into raises() using EitherType. #70

Sign in to view logs

Merge raisesCondition() into raises() using EitherType.

Merge raisesCondition() into raises() using EitherType. #70

Triggered via pull request December 15, 2023 19:42
@player-03player-03
opened #127
player-03:raises-condition
Status Failure
Total duration 3m 22s
Artifacts –

build.yml

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

Annotations

107 errors and 12 warnings
build (ubuntu-latest, latest)
Process completed with exit code 1.
build (ubuntu-latest, latest)
Process completed with exit code 1.
build (ubuntu-latest, latest)
Process completed with exit code 1.
build (ubuntu-latest, latest)
Process completed with exit code 1.
build (ubuntu-latest, latest)
Process completed with exit code 1.
build (ubuntu-latest, latest)
Process completed with exit code 1.
build (ubuntu-latest, latest)
Process completed with exit code 1.
build (ubuntu-latest, latest)
Process completed with exit code 1.
build (ubuntu-latest, latest)
Process completed with exit code 1.
build (ubuntu-latest, 4.3.3)
Process completed with exit code 1.
build (ubuntu-latest, 4.3.3)
Process completed with exit code 1.
build (ubuntu-latest, 4.3.3)
Process completed with exit code 1.
build (ubuntu-latest, 4.3.3)
Process completed with exit code 1.
build (ubuntu-latest, 4.3.3)
Process completed with exit code 1.
build (ubuntu-latest, 4.3.3)
Process completed with exit code 1.
build (ubuntu-latest, 4.3.3)
Process completed with exit code 1.
build (ubuntu-latest, 4.3.3)
Process completed with exit code 1.
build (ubuntu-latest, 4.3.3)
Process completed with exit code 1.
build (windows-latest, 4.1.5)
Process completed with exit code 1.
build (windows-latest, 4.1.5)
Process completed with exit code 1.
build (windows-latest, 4.1.5)
Process completed with exit code 1.
build (windows-latest, 4.1.5)
Process completed with exit code 1.
build (windows-latest, 4.1.5)
Process completed with exit code 1.
build (windows-latest, 4.1.5)
Process completed with exit code 1.
build (windows-latest, 4.1.5)
Process completed with exit code 1.
build (windows-latest, 4.1.5)
Process completed with exit code 1.
build (windows-latest, 4.3.3)
Process completed with exit code 1.
build (windows-latest, 4.3.3)
Process completed with exit code 1.
build (windows-latest, 4.3.3)
Process completed with exit code 1.
build (windows-latest, 4.3.3)
Process completed with exit code 1.
build (windows-latest, 4.3.3)
Process completed with exit code 1.
build (windows-latest, 4.3.3)
Process completed with exit code 1.
build (windows-latest, 4.3.3)
Process completed with exit code 1.
build (windows-latest, 4.3.3)
Process completed with exit code 1.
build (windows-latest, 4.3.3)
Process completed with exit code 1.
build (windows-latest, latest)
Process completed with exit code 1.
build (windows-latest, latest)
Process completed with exit code 1.
build (windows-latest, latest)
Process completed with exit code 1.
build (windows-latest, latest)
Process completed with exit code 1.
build (windows-latest, latest)
Process completed with exit code 1.
build (windows-latest, latest)
Process completed with exit code 1.
build (windows-latest, latest)
Process completed with exit code 1.
build (windows-latest, latest)
Process completed with exit code 1.
build (windows-latest, latest)
Process completed with exit code 1.
build (windows-latest, 4.2.5)
Process completed with exit code 1.
build (windows-latest, 4.2.5)
Process completed with exit code 1.
build (windows-latest, 4.2.5)
Process completed with exit code 1.
build (windows-latest, 4.2.5)
Process completed with exit code 1.
build (windows-latest, 4.2.5)
Process completed with exit code 1.
build (windows-latest, 4.2.5)
Process completed with exit code 1.
build (windows-latest, 4.2.5)
Process completed with exit code 1.
build (windows-latest, 4.2.5)
Process completed with exit code 1.
build (windows-latest, 4.2.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.1.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.1.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.1.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.1.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.1.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.1.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.1.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.1.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.1.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.2.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.2.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.2.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.2.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.2.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.2.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.2.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.2.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.2.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.2.5)
Process completed with exit code 1.
build (macos-latest, 4.1.5)
Process completed with exit code 1.
build (macos-latest, 4.1.5)
Process completed with exit code 1.
build (macos-latest, 4.1.5)
Process completed with exit code 1.
build (macos-latest, 4.1.5)
Process completed with exit code 1.
build (macos-latest, 4.1.5)
Process completed with exit code 1.
build (macos-latest, 4.1.5)
Process completed with exit code 1.
build (macos-latest, 4.1.5)
Process completed with exit code 1.
build (macos-latest, 4.1.5)
Process completed with exit code 1.
build (macos-latest, latest)
Process completed with exit code 1.
build (macos-latest, latest)
Process completed with exit code 1.
build (macos-latest, latest)
Process completed with exit code 1.
build (macos-latest, latest)
Process completed with exit code 1.
build (macos-latest, latest)
Process completed with exit code 1.
build (macos-latest, latest)
Process completed with exit code 1.
build (macos-latest, latest)
Process completed with exit code 1.
build (macos-latest, latest)
Process completed with exit code 1.
build (macos-latest, latest)
Process completed with exit code 1.
build (macos-latest, 4.2.5)
Process completed with exit code 1.
build (macos-latest, 4.2.5)
Process completed with exit code 1.
build (macos-latest, 4.2.5)
Process completed with exit code 1.
build (macos-latest, 4.2.5)
Process completed with exit code 1.
build (macos-latest, 4.2.5)
Process completed with exit code 1.
build (macos-latest, 4.2.5)
Process completed with exit code 1.
build (macos-latest, 4.2.5)
Process completed with exit code 1.
build (macos-latest, 4.2.5)
Process completed with exit code 1.
build (macos-latest, 4.2.5)
Process completed with exit code 1.
build (macos-latest, 4.3.3)
Process completed with exit code 1.
build (macos-latest, 4.3.3)
Process completed with exit code 1.
build (macos-latest, 4.3.3)
Process completed with exit code 1.
build (macos-latest, 4.3.3)
Process completed with exit code 1.
build (macos-latest, 4.3.3)
Process completed with exit code 1.
build (macos-latest, 4.3.3)
Process completed with exit code 1.
build (macos-latest, 4.3.3)
Process completed with exit code 1.
build (macos-latest, 4.3.3)
Process completed with exit code 1.
build (macos-latest, 4.3.3)
Process completed with exit code 1.
build (ubuntu-latest, latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (ubuntu-latest, 4.3.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (windows-latest, 4.1.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (windows-latest, 4.3.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (windows-latest, latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (windows-latest, 4.2.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (ubuntu-latest, 4.1.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (ubuntu-latest, 4.2.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (macos-latest, 4.1.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (macos-latest, latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (macos-latest, 4.2.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (macos-latest, 4.3.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/