Skip to content

Hex and string built-ins #418

Hex and string built-ins

Hex and string built-ins #418

Triggered via pull request October 9, 2023 18:50
Status Failure
Total duration 15m 11s
Artifacts

test.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 20 warnings
Test Suite: etk-asm/src/parse/macros.rs#L49
no variant or associated item named `inline_hex` found for enum `Rule` in the current scope
Test Suite: etk-asm/src/parse/macros.rs#L60
no variant or associated item named `inline_string` found for enum `Rule` in the current scope
Test Suite
could not compile `etk-asm` (lib) due to 2 previous errors
Test Suite
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Check: etk-asm/src/parse/macros.rs#L49
no variant or associated item named `inline_hex` found for enum `Rule` in the current scope
Check: etk-asm/src/parse/macros.rs#L60
no variant or associated item named `inline_string` found for enum `Rule` in the current scope
Check
could not compile `etk-asm` (lib) due to 2 previous errors
Check
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Rustfmt
could not compile `etk-asm` (lib) due to 3 previous errors
Rustfmt
Unable to create clippy annotations! Reason: HttpError: Resource not accessible by integration
Rustfmt: etk-asm/src/parse/macros.rs#L49
no variant or associated item named `inline_hex` found for enum `parse::parser::Rule` in the current scope
Rustfmt: etk-asm/src/parse/macros.rs#L60
no variant or associated item named `inline_string` found for enum `parse::parser::Rule` in the current scope
Rustfmt
Exiting due to clippy errors
Test Suite
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@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 Suite
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 Suite
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 Suite
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 Suite
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 Suite
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Check
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/
Check
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/
Check
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/
Check
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/
Rustfmt
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Rustfmt
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/
Rustfmt
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/
Rustfmt
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/
Rustfmt
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/
Rustfmt
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Rustfmt
It seems that this Action is executed from the forked repository.
Rustfmt
GitHub Actions are not allowed to create Check annotations, when executed for a forked repos. See https://github.com/actions-rs/clippy-check/issues/2 for details.