Skip to content

ci: save space

ci: save space #183

Triggered via pull request December 21, 2024 09:41
Status Cancelled
Total duration 35m 40s
Artifacts

ci.yml

on: pull_request
Matrix: build
Matrix: test
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 10 warnings
build (1.79.0)
Process completed with exit code 101.
build
The job was canceled because "_1_79_0" failed.
test (1.79.0)
Process completed with exit code 101.
test
The job was canceled because "_1_79_0" failed.
coverage
Canceling since a higher priority waiting request for 'ci-refs/pull/40/merge' exists
coverage
The operation was canceled.
unexpected `cfg` condition value: `anchor-debug`: programs/example_program/src/lib.rs#L5
warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `program` crate for guidance on how handle this unexpected cfg = help: the attribute macro `program` may come from an old version of the `anchor_attribute_program` crate, try updating your dependency with `cargo update -p anchor_attribute_program` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = note: this warning originates in the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info)
unexpected `cfg` condition value: `anchor-debug`: programs/example_program/src/lib.rs#L5
warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)
unexpected `cfg` condition value: `anchor-debug`: programs/example_program/src/lib.rs#L5
warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)
unexpected `cfg` condition value: `anchor-debug`: programs/example_program/src/lib.rs#L5
warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)
unexpected `cfg` condition value: `anchor-debug`: programs/example_program/src/lib.rs#L5
warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)
unexpected `cfg` condition value: `anchor-debug`: programs/example_program/src/lib.rs#L5
warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)
unexpected `cfg` condition value: `anchor-debug`: programs/example_program/src/lib.rs#L5
warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)
unexpected `cfg` condition value: `anchor-debug`: programs/example_program/src/lib.rs#L20
warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:20:10 | 20 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)
unexpected `cfg` condition value: `anchor-debug`: programs/example_program/src/lib.rs#L26
warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:26:10 | 26 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)
use of deprecated struct `solana_sdk::stake::config::Config`: Please use `solana_sdk::stake::state::warmup_cooldown_rate()` instead: crates/wasm_client_solana/src/solana_config_program.rs#L11
warning: use of deprecated struct `solana_sdk::stake::config::Config`: Please use `solana_sdk::stake::state::warmup_cooldown_rate()` instead --> crates/wasm_client_solana/src/solana_config_program.rs:11:32 | 11 | use solana_sdk::stake::config::Config as StakeConfig; | ^^^^^^ | = note: `#[warn(deprecated)]` on by default