Skip to content

Multiple Choice Veto #4392

Multiple Choice Veto

Multiple Choice Veto #4392

Triggered via pull request December 2, 2023 22:45
Status Failure
Total duration 4m 54s
Artifacts

basic.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 21 warnings
Lints: contracts/pre-propose/dao-pre-propose-multiple/src/tests.rs#L57
missing field `veto` in initializer of `dao_proposal_multiple::msg::InstantiateMsg`
Lints: contracts/pre-propose/dao-pre-propose-multiple/src/tests.rs#L1039
missing field `veto` in initializer of `dao_proposal_multiple::msg::InstantiateMsg`
Lints: contracts/pre-propose/dao-pre-propose-multiple/src/tests.rs#L1101
missing field `veto` in initializer of `dao_proposal_multiple::msg::InstantiateMsg`
Lints
could not compile `dao-pre-propose-multiple` (lib test) due to 3 previous errors
Lints
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Test Suite: contracts/pre-propose/dao-pre-propose-multiple/src/tests.rs#L57
missing field `veto` in initializer of `dao_proposal_multiple::msg::InstantiateMsg`
Test Suite: contracts/pre-propose/dao-pre-propose-multiple/src/tests.rs#L1039
missing field `veto` in initializer of `dao_proposal_multiple::msg::InstantiateMsg`
Test Suite: contracts/pre-propose/dao-pre-propose-multiple/src/tests.rs#L1101
missing field `veto` in initializer of `dao_proposal_multiple::msg::InstantiateMsg`
Test Suite
could not compile `dao-pre-propose-multiple` (lib test) due to 3 previous errors
Test Suite
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Lints
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/
Lints
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Lints
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/
Lints
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/
Lints
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/
Lints
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/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"`
Test Suite
output filename collision.
Test Suite
output filename collision.
Test Suite
output filename collision.
Test Suite
output filename collision.
Test Suite
output filename collision.
Test Suite
output filename collision.
Test Suite
output filename collision.
Test Suite
output filename collision.
Test Suite
output filename collision.