Skip to content

fix recovering from an error in set_seq #175

fix recovering from an error in set_seq

fix recovering from an error in set_seq #175

Triggered via pull request October 7, 2023 14:36
Status Failure
Total duration 43s
Artifacts

build.yml

on: pull_request
cargo-fmt
14s
cargo-fmt
cargo-clippy
32s
cargo-clippy
Check rustdoc intra-doc links
34s
Check rustdoc intra-doc links
release-tests-ubuntu
0s
release-tests-ubuntu
release-tests-ubuntu-all-features
0s
release-tests-ubuntu-all-features
release-tests-ubuntu-ed25519
0s
release-tests-ubuntu-ed25519
cargo-audit
0s
cargo-audit
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
cargo-fmt
Process completed with exit code 1.
cargo-fmt
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
cargo-clippy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check rustdoc intra-doc links
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/