Try runtime fixes #156
Triggered via pull request
December 4, 2023 11:52
Status
Failure
Total duration
1d 11h 34m 26s
Artifacts
–
Annotations
3 errors and 5 warnings
try-runtime
Process completed with exit code 101.
|
test-features
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
cargo-fmt
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
try-runtime
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/
|
try-runtime
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/
|
try-runtime
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/
|
try-runtime
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/
|
try-runtime
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/
|