Unit & Integration testing #31

Sign in to view logs

Triggered via pull request October 22, 2023 18:32

synchronize #4

testing-setup

Status Failure

Total duration 3m 24s

Artifacts –

rust.yml

on: pull_request

Verify code Fromatting

Lint with clippy

Matrix: Test and Build

Annotations

2 errors and 6 warnings

Test and Build (ubuntu-latest)

Process completed with exit code 1.

Test and Build (macos-latest)

The operation was canceled.

Test and Build (ubuntu-latest)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Test and Build (ubuntu-latest)

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Test and Build (ubuntu-latest)

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Test and Build (ubuntu-latest)

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Test and Build (ubuntu-latest)

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Test and Build (macos-latest)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/