chore: separate gh action jobs for running tests and checking cosmwasm compilation #15
Triggered via pull request
September 15, 2023 02:21
Status
Failure
Total duration
4m 18s
Artifacts
–
Annotations
11 errors and 16 warnings
Cosmowasm Compilation
can't find crate for `core`
|
Cosmowasm Compilation
can't find crate for `compiler_builtins`
|
Cosmowasm Compilation
can't find crate for `core`
|
Cosmowasm Compilation
can't find crate for `core`
|
Cosmowasm Compilation
can't find crate for `core`
|
Cosmowasm Compilation
can't find crate for `core`
|
Cosmowasm Compilation
can't find crate for `core`
|
Cosmowasm Compilation
can't find crate for `core`
|
Cosmowasm Compilation
can't find crate for `core`
|
Cosmowasm Compilation
unresolved imports `crate::generated::consts`, `core::cmp::Ordering`, `crate::Cmp`, `crate::Equal`, `crate::Greater`, `crate::Less`, `crate::NonZero`, `crate::PowerOfTwo`, `crate::Zero`, `crate::Min`, `crate::Max`, `crate::consts::N1`, `crate::consts::P1`, `crate::consts::U0`, `crate::consts::U1`, `crate::Cmp`, `crate::Equal`, `crate::Greater`, `crate::Less`, `crate::NonZero`, `crate::Pow`, `crate::PowerOfTwo`, `crate::ToInt`, `crate::Zero`, `crate::PartialDiv`, `crate::Quot`, `crate::Gcd`, `crate::Gcf`, `crate::Max`, `crate::Maximum`, `crate::Min`, `crate::Minimum`, `crate::Equal`
|
Test Suite
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/axelar-amplifier/axelar-amplifier/.github/actions/build'. Did you forget to run actions/checkout before running your local action?
|
Cosmowasm Compilation
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
|
Cosmowasm Compilation
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
|
Cosmowasm Compilation
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/
|
Cosmowasm Compilation
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/
|
Cosmowasm Compilation
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/
|
Cosmowasm Compilation
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 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 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/
|
Linting
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
|
Linting
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/
|
Linting
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/
|
Linting
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/
|
Linting
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/
|